CVE-2022-26417
CVE-2022-26417 is a high-severity vulnerability in Omron Cx-position with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-416.
Key facts
- Severity: High (CVSS 3.x base score 7.8)
- CVSS v2: 6.8
- EPSS exploit prediction: 1% (69th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-416
- Affected product: Omron Cx-position
- Published:
- Last modified:
Description
Omron CX-Position (versions 2.5.3 and prior) is vulnerable to a use after free memory condition while processing a specific project file, which may allow an attacker to execute arbitrary code.
Frequently asked questions
- What is CVE-2022-26417?
- Omron CX-Position (versions 2.5.3 and prior) is vulnerable to a use after free memory condition while processing a specific project file, which may allow an attacker to execute arbitrary code.
- How severe is CVE-2022-26417?
- CVE-2022-26417 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2022-26417 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (69th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2022-26417?
- CVE-2022-26417 affects Omron Cx-position. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2022-26417?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2022-26417 published?
- CVE-2022-26417 was published on 2022-04-01 and last updated on 2026-06-17.
References
- https://www.cisa.gov/uscert/ics/advisories/icsa-22-088-02
- https://www.zerodayinitiative.com/advisories/ZDI-22-578/
Affected products (1)
- cpe:2.3:a:omron:cx-position:*:*:*:*:*:*:*:*
More vulnerabilities in Omron Cx-position
- CVE-2020-27261 — High (CVSS 8.8): The Omron CX-One Version 4.60 and prior is vulnerable to a stack-based buffer overflow, which may allow an attacker to…
- CVE-2020-27259 — High (CVSS 8.8): The Omron CX-One Version 4.60 and prior may allow an attacker to supply a pointer to arbitrary memory locations, which…
- CVE-2022-26419 — High (CVSS 7.8): Omron CX-Position (versions 2.5.3 and prior) is vulnerable to multiple stack-based buffer overflow conditions while…
- CVE-2022-26022 — High (CVSS 7.8): Omron CX-Position (versions 2.5.3 and prior) is vulnerable to an out-of-bounds write while processing a specific…
- CVE-2022-25959 — High (CVSS 7.8): Omron CX-Position (versions 2.5.3 and prior) is vulnerable to memory corruption while processing a specific project…
- CVE-2020-27257 — High (CVSS 7.8): This vulnerability allows local attackers to execute arbitrary code due to the lack of proper validation of…
All CVEs affecting Omron Cx-position →
Other CWE-416 (Use After Free) vulnerabilities
- CVE-2026-13782 — Critical (CVSS 10.0): Use after free in Browser in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the…
- CVE-2026-4725 — Critical (CVSS 10.0): Sandbox escape due to use-after-free in the Graphics: Canvas2D component. This vulnerability was fixed in Firefox 149…
- CVE-2026-4688 — Critical (CVSS 10.0): Sandbox escape due to use-after-free in the Disability Access APIs component. This vulnerability was fixed in Firefox…
- CVE-2025-24085 — Critical (CVSS 10.0): A use after free issue was addressed with improved memory management. This issue is fixed in iOS 18.3 and iPadOS 18.3,…
- CVE-2024-43102 — Critical (CVSS 10.0): Concurrent removals of certain anonymous shared memory mappings by using the UMTX_SHM_DESTROY sub-request of…
- CVE-2021-32495 — Critical (CVSS 10.0): Radare2 has a use-after-free vulnerability in pyc parser's get_none_object function. Attacker can read freed memory…