Critical severity · published Jan 29, 2026
CVE-2026-1188
In the Eclipse OMR port library component since release 0.2.0, an API function to return the textual names of all supported processor features was not accounting for the separator…
9.8
CVSS
0.5%
EPSS
No
On KEV
Description
In the Eclipse OMR port library component since release 0.2.0, an API function to return the textual names of all supported processor features was not accounting for the separator inserted between processor features. If the output buffer supplied to this function was incorrectly sized, failing to account for the separator when determining when a write to the buffer was safe could lead to a buffer overflow. This issue is fixed in Eclipse OMR version 0.8.0.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.5% · higher than 42% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
OM
Omr · Eclipse
0.2 before 0.8.0 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-1188
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-1188
Issue Tracking
https://github.com/eclipse-omr/omr/pull/8082
More from Omr
8.1
CVE-2025-14549
In the Eclipse OMR compiler component, since release 0.7.0, an optimization enabled for Eclipse OpenJ9 consumers of OMR on Z processors incorrectly handles NUL (0x00) characters…
7.8
CVE-2025-1471
In Eclipse OMR versions 0.2.0 to 0.4.0, some of the z/OS atoe print functions use a constant length buffer for string conversion
7.8
CVE-2019-11773
Prior to 0.1, AIX builds of Eclipse OMR contain unused RPATHs which may facilitate code injection and privilege elevation by local users
7.5
CVE-2026-16243
Eclipse OMR : arraycmp SIMD implementation does not check if the number of bytes to compare is zero
7.4
CVE-2019-11774
Prior to 0.1, all builds of Eclipse OMR contain a bug where the loop versioner may fail to privatize a value that is pulled out of the loop by versioning - for example if there is…