# CVE-2025-55089: Eclipse ThreadX FileX RAM disk driver buffer overflow

> A buffer overflow in the FileX RAM disk driver allows remote code execution via crafted packets, affecting Eclipse ThreadX users.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2025
- **Updated:** 16 Oct 2025
- **Also known as:** GHSA-467v-6j75-3j7g

## What is CVE-2025-55089?

CVE-2025-55089 is a critical memory corruption vulnerability in Eclipse Foundation FileX, published on 16 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In FileX before 6.4.2, the file support module for Eclipse Foundation ThreadX, there was a possible buffer overflow in the FileX RAM disk driver. It could cause a remote execurtion after receiving a crafted sequence of packets

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Eclipse Threadx Filex.

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

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

## Is CVE-2025-55089 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55089 is a critical memory corruption vulnerability in Eclipse Foundation FileX, published on 16 Oct 2025. 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-2025-55089 in the wild and no public exploit code.

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

## Sources

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

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