Eclipse Omr

Buffer Overflow in Eclipse OMR 0.2.0-0.7.9 via Feature Name API fixed in 0.8.0
CVE-2026-1188 - January 29, 2026

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.

Incorrect Calculation of Buffer Size

Eclipse OMR 0.8.0: UTF-8 NUL truncation bug fixed (Z processors)
CVE-2025-14549 - December 15, 2025

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 first NUL byte and all subsequent characters, and thereby exposing a possible buffer over-read problem. This issue is fixed in Eclipse OMR version 0.8.0.

Out-of-bounds Read

Eclipse OMR <=0.4.0 Buffer Overflow in Z/OS ATOE Print Functions
CVE-2025-1471 7.8 - High - February 21, 2025

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.

Null Ptr Deref in Eclipse OMR OAE atoe lib (pre v0.5.0)
CVE-2025-1470 5.5 - Medium - February 21, 2025

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 functions handle NULL return values and memory allocation failures correctly.

Prior to 0.1, AIX builds of Eclipse OMR contain unused RPATHs
CVE-2019-11773 7.8 - High - September 12, 2019

Prior to 0.1, AIX builds of Eclipse OMR contain unused RPATHs which may facilitate code injection and privilege elevation by local users.

DLL preloading

Prior to 0.1, all builds of Eclipse OMR contain a bug where the loop versioner may fail to privatize a value
CVE-2019-11774 7.4 - High - September 12, 2019

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 of the field and subsequently the loop to see a modified field value without retesting the condition moved out of the loop. This can lead to a variety of different issues but read out of array bounds is one major consequence of these problems.

TOCTTOU