# CVE-2026-1188: Memory corruption in Eclipse OMR

> A buffer overflow in Eclipse OMR's port library allows attackers to execute arbitrary code or cause denial of service via improperly sized output buffers.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jan 2026
- **Updated:** 29 Jan 2026
- **Also known as:** GHSA-x24c-w26v-w8jg, openSUSE-SU-2026:10788-1, openSUSE-SU-2026:10789-1, openSUSE-SU-2026:10790-1, openSUSE-SU-2026:10791-1, openSUSE-SU-2026:10792-1

## What is CVE-2026-1188?

CVE-2026-1188 is a medium-severity memory corruption vulnerability in Eclipse OMR, published on 29 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-131 (Incorrect Calculation of Buffer Size)

## Which versions are affected by CVE-2026-1188?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `java-11-openj9` | openSUSE:Tumbleweed | All versions | 11.0.31.0-2.1 |
| `java-17-openj9` | openSUSE:Tumbleweed | All versions | 17.0.19.0-2.1 |
| `java-1_8_0-openj9` | openSUSE:Tumbleweed | All versions | 1.8.0.492-2.1 |
| `java-21-openj9` | openSUSE:Tumbleweed | All versions | 21.0.11.0-2.1 |
| `java-25-openj9` | openSUSE:Tumbleweed | All versions | 25.0.3.0-2.1 |

Products: Eclipse Omr.

## How do I fix CVE-2026-1188?

Upgrade to a fixed version.

## Is CVE-2026-1188 being exploited?

There is no known exploitation of CVE-2026-1188 in the wild and no public exploit code.

## Other vulnerabilities in Eclipse OMR

- [CVE-2019-11773](https://insights.sbomify.com/CVE-2019-11773/): Privilege escalation in Eclipse OMR (high 7.8)
- [CVE-2019-11774](https://insights.sbomify.com/CVE-2019-11774/): Race condition in Eclipse OMR (high 7.4)
- [CVE-2025-1471](https://insights.sbomify.com/CVE-2025-1471/): Eclipse OMR: Buffer overflow vulnerability (high 7.1)
- [CVE-2025-14549](https://insights.sbomify.com/CVE-2025-14549/): OMR on Z processors Exposing a possible buffer over-read problem (medium 6.9)
- [CVE-2026-16243](https://insights.sbomify.com/CVE-2026-16243/): Eclipse OMR : arraycmp SIMD implementation does not check if the number of bytes to compare is zero (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1188 and fix it if it is affected.

What it is: CVE-2026-1188 is a medium-severity memory corruption vulnerability in Eclipse OMR, published on 29 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1188 in the wild and no public exploit code.

Affected product: Eclipse OMR. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1188/ (Markdown: https://insights.sbomify.com/CVE-2026-1188/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1188
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1188
- OSV: https://osv.dev/vulnerability/CVE-2026-1188

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1188/
Summaries are generated and may contain mistakes; the official description above is the record.