# CVE-2025-1471: Eclipse OMR: Buffer overflow vulnerability

> A buffer overflow in Eclipse OMR z/OS print functions allows attackers to cause memory corruption, potentially leading to code execution or denial of service.

- **Severity:** High 7.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2025
- **Updated:** 25 Feb 2025
- **Also known as:** GHSA-w5mv-5x6q-jgmp

## What is CVE-2025-1471?

CVE-2025-1471 is a high-severity memory corruption vulnerability in Eclipse OMR, published on 21 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2025-1471?

It affects 1 product.


Products: Eclipse Omr.

## How do I fix CVE-2025-1471?

No fix has been published for CVE-2025-1471 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-1471 being exploited?

There is no known exploitation of CVE-2025-1471 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-2026-1188](https://insights.sbomify.com/CVE-2026-1188/): Memory corruption in Eclipse OMR (medium 6.9)
- [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-2025-1471 and fix it if it is affected.

What it is: CVE-2025-1471 is a high-severity memory corruption vulnerability in Eclipse OMR, published on 21 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1471 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-2025-1471/ (Markdown: https://insights.sbomify.com/CVE-2025-1471/index.md)
```

## Sources

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

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