CVE-2018-18989 json
In CX-One Versions 4.42 and prior (CX-Programmer Versions 9.66 and prior and CX-Server Versions 5.0.23 and prior), when processing project…
published 2018-12-04 7 y ago modified 2026-06-17 4 mo ago also EUVD-2018-10693
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
In CX-One Versions 4.42 and prior (CX-Programmer Versions 9.66 and prior and CX-Server Versions 5.0.23 and prior), when processing project files, the application fails to check if it is referencing freed memory. An attacker could use a specially crafted project file to exploit and execute code under the privileges of the application.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-18-338-01 updated cvss 5.8
Omron CX-One
-
Omron CX-Programmer <= 9.66 Omron CX-Server <= 5.0.23affected: vendor fix, mitigation “Omron has released an updated version of CX-One to address the reported vulnerabilities. These releases are available through the CX-One auto-update service.”
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
1.63% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- n/a CX-One (CX-Programmer and CX-Server)
Classification
- Weakness
-
- CWE-416 Use After Free
References
-
ics-cert.us-cert.gov
/advisories/ICSA-18-338-01
third-party-advisory, us-government-resource
-
securityfocus.com
/bid/106106
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-18989
- NVD CVE-2018-18989
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.