# CVE-2026-92154: F´: File size bounds bypass in Svc::FileUplink via unsigned integer overflow in DATA packet validation

> An attacker can bypass file size bounds in F Prime's FileUplink service via integer overflow, causing data corruption or resource exhaustion.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-wx8q-q5gx-f54p

## What is CVE-2026-92154?

CVE-2026-92154 is a high-severity vulnerability in nasa fprime, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

F´ (F Prime) is a framework that enables development and deployment of spaceflight and other embedded software applications. Prior to 4.2.0, Svc::FileUplink handleDataPacket offset and size validation is vulnerable because the component checks byteOffset plus dataSize with wrapping U32 arithmetic and then seeks to the large attacker-controlled offset before writing. When a file-uplink DATA packet supplies a byteOffset and dataSize whose unsigned sum wraps below the declared file size, data can be written beyond the declared upload size, causing file integrity loss and potentially large sparse-file growth or resource exhaustion. This issue is fixed in version 4.2.0.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

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

## Is CVE-2026-92154 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92154 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92154 is a high-severity vulnerability in nasa fprime, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92154 exists.

Affected product: nasa fprime. 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-92154/ (Markdown: https://insights.sbomify.com/CVE-2026-92154/index.md)
```

## Sources

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

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