Eclipse Omr vulnerabilities

6 known vulnerabilities affecting eclipse/omr.

Total CVEs
6
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
HIGH3MEDIUM3

Vulnerabilities

Page 1 of 1
CVE-2026-1188MEDIUMCVSS 6.9≥ 0.2, < 0.8.02026-01-29
CVE-2026-1188 [MEDIUM] CWE-131 CVE-2026-1188: In the Eclipse OMR port library component since release 0.2.0, an API function to return the textual 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
nvd
CVE-2025-14549MEDIUMCVSS 6.9v0.7.02025-12-15
CVE-2025-14549 [MEDIUM] CWE-125 CVE-2025-14549: In the Eclipse OMR compiler component, since release 0.7.0, an optimization enabled for Eclipse Open 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 during the Latin-compatible charset (UTF-8, ISO8859-1, ASCII, etc) to IBM-1047/037 translation sequence. This can cause the output byte array to be truncated, discarding the
nvd
CVE-2025-1471HIGHCVSS 7.1≥ 0.2.0, ≤ 0.4.02025-02-21
CVE-2025-1471 [HIGH] CWE-787 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 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. If the input format string and arguments are larger than the buffer size then buffer overflow occurs. Beginning in version 0.5.0, the conversion buffers are sized correctly and checked appropriately to prevent buffer overflows
nvd
CVE-2025-1470MEDIUMCVSS 5.1≤ 0.4.02025-02-21
CVE-2025-1470 [MEDIUM] CWE-476 CVE-2025-1470: In Eclipse OMR, from the initial contribution to version 0.4.0, some OMR internal port library and u In Eclipse OMR, from the initial contribution to version 0.4.0, some OMR internal port library and utilities consumers of z/OS atoe functions do not check their return values for NULL memory pointers or for memory allocation failures. This can lead to NULL pointer dereference crashes. Beginning in version 0.5.0, internal OMR consumers of atoe function
nvd
CVE-2019-11773HIGHCVSS 7.8fixed in 0.12019-09-12
CVE-2019-11773 [HIGH] CWE-264 CVE-2019-11773: Prior to 0.1, AIX builds of Eclipse OMR contain unused RPATHs which may facilitate code injection an Prior to 0.1, AIX builds of Eclipse OMR contain unused RPATHs which may facilitate code injection and privilege elevation by local users.
nvd
CVE-2019-11774HIGHCVSS 7.4fixed in 0.12019-09-12
CVE-2019-11774 [HIGH] CWE-367 CVE-2019-11774: Prior to 0.1, all builds of Eclipse OMR contain a bug where the loop versioner may fail to privatize 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 a condition that is moved out of the loop that reads a field we may not privatize the value of that field in the modified copy of the loop allowing the test to see one value
nvd