# CVE-2025-4447: Buffer Overflow in Eclipse OpenJ9

> A stack-based buffer overflow in Eclipse OpenJ9 allows attackers to execute arbitrary code or cause denial of service by modifying a file read during JVM startup.

- **Severity:** High 7.0 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:H/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2025
- **Updated:** 10 May 2025
- **Also known as:** GHSA-wmvg-c6fc-33c8, openSUSE-SU-2025:15231-1

## What is CVE-2025-4447?

CVE-2025-4447 is a high-severity memory corruption vulnerability in Eclipse Foundation OpenJ9, published on 9 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Eclipse OpenJ9 versions up to 0.51, when used with OpenJDK version 8 a stack based buffer overflow can be caused by modifying a file on disk that is read when the JVM starts.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `java-1_8_0-openj9` | openSUSE:Tumbleweed | All versions | 1.8.0.452-3.1 |

Products: Eclipse Openj9.

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

Apply the vendor's patch.

## Is CVE-2025-4447 being exploited?

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

## Other vulnerabilities in Eclipse Foundation OpenJ9

- [CVE-2021-41035](https://insights.sbomify.com/CVE-2021-41035/): Security feature bypass in Eclipse OMR (critical 9.8)
- [CVE-2020-27221](https://insights.sbomify.com/CVE-2020-27221/): Memory corruption in Eclipse OpenJ9 (critical 9.8)
- [CVE-2019-11772](https://insights.sbomify.com/CVE-2019-11772/): Memory corruption in Eclipse OpenJ9 (critical 9.8)
- [CVE-2018-12547](https://insights.sbomify.com/CVE-2018-12547/): Memory corruption in Eclipse OpenJ9 (critical 9.8)
- [CVE-2018-12549](https://insights.sbomify.com/CVE-2018-12549/): Null dereference in Eclipse OpenJ9 (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4447 and fix it if it is affected.

What it is: CVE-2025-4447 is a high-severity memory corruption vulnerability in Eclipse Foundation OpenJ9, published on 9 May 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-4447 in the wild and no public exploit code.

Affected product: Eclipse Foundation OpenJ9. 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-4447/ (Markdown: https://insights.sbomify.com/CVE-2025-4447/index.md)
```

## Sources

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

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