# CVE-2026-92160: F´: SendPartial Integer Overflow Leading to Assertion DoS

> An attacker can cause a denial of service in F Prime embedded systems by triggering an integer overflow in file downlink operations.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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-8r3j-ghrh-55mw

## What is CVE-2026-92160?

CVE-2026-92160 is a medium-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.3.0, Svc::FileDownlink SendPartial range validation is vulnerable because the wrapping sum bypasses file-range validation, becomes m_endOffset, and leaves m_byteOffset greater than the wrapped end offset. When an existing source file is larger than the supplied startOffset and a caller able to issue SendPartial supplies a length whose U32 sum with that offset wraps, the first data-packet send reaches FW_ASSERT and aborts or resets the process, causing denial of service. This issue is fixed in version 4.3.0.

Weakness: CWE-617 (Reachable Assertion), CWE-190 (Integer Overflow or Wraparound)

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


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

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

## Is CVE-2026-92160 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92160 is a medium-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: There is no known exploitation of CVE-2026-92160 in the wild and no public exploit code.

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-92160/ (Markdown: https://insights.sbomify.com/CVE-2026-92160/index.md)
```

## Sources

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

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