# CVE-2026-92153: F´: Arbitrary File Write in Svc::FileUplink via attacker-controlled StartPacket.destinationPath

> Attackers can write or overwrite arbitrary files via path traversal in F Prime's FileUplink service, compromising system integrity and availability.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L`)
- **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-5rfj-hw2g-vwmv

## What is CVE-2026-92153?

CVE-2026-92153 is a high-severity path traversal 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::FileUplink handling of Fw::FilePacket::StartPacket destination paths FileUplink copies the packet-controlled destinationPath and opens it for writing without canonicalization or confinement to an upload directory. When a peer able to send file-uplink packets supplies an absolute, traversing, or otherwise attacker-selected writable destination path, files can be created or overwritten at attacker-selected writable filesystem locations, affecting integrity and potentially availability. This issue is fixed in version 4.3.0.

Weakness: CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-92153 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92153 is a high-severity path traversal 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-92153 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-92153/ (Markdown: https://insights.sbomify.com/CVE-2026-92153/index.md)
```

## Sources

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

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