CVE-2026-92153
7.1HighPublished 14 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Impact
- High impact on integrity
- Weakness
- CWE-22, CWE-73
Impact
Authenticated network peers can create or overwrite arbitrary writable files on the target filesystem. They only need permissions to send file-uplink packets to the application.
Root cause
The Svc::FileUplink component writes destination files directly from packet-supplied paths without canonicalizing them or restricting them to a specific upload directory.
Affected systems
F´ (F Prime) prior to 4.3.0
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
Fix & remediation
Upgrade to F´ version 4.3.0 or later. If patching immediately is not possible, restrict or disable peer network access to the file-uplink service.
$ git checkout v4.3.0AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD 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.