CVE-2026-92158
What it is
F´ (F Prime) is a framework that enables development and deployment of spaceflight and other embedded software applications. Prior to 4.2.0, Svc::FpySequencer STORE directive stack write validation the bounds check adds attacker-controlled offset and size before memcpy, allowing integer wraparound to make an out-of-range destination appear valid. When a sequence-controlled STORE directive supplies a stack offset and size whose U32 sum wraps, memcpy can write outside the sequencer stack, causing memory corruption, denial of service, and potentially code execution. This issue is fixed in version 4.2.0.
At a glance
- Exploitability
- Can be exploited over the network with an admin-level account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.9% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.9% in the next 30 days (EPSS).
- Severity: 7.2 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.9% · EPSS, next 30 days
- Weakness
- CWE-190 · Integer overflow
- Record status
- Deferred
Attack profile CVSS 3.1 · 7.2
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-92158.md and follow it. Check whether this project is affected by CVE-2026-92158. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/nasa/fprime/commit/7527430d9ae7c88f3d649d376a45c866b0aed595
- https://github.com/nasa/fprime/pull/4534
- https://github.com/nasa/fprime/releases/tag/v4.2.0
- https://github.com/nasa/fprime/security/advisories/GHSA-vfwv-3qv7-jjjq
- https://github.com/nasa/fprime/security/advisories/GHSA-vfwv-3qv7-jjjq
References
- https://github.com/nasa/fprime/commit/7527430d9ae7c88f3d649d376a45c866b0aed595
- https://github.com/nasa/fprime/pull/4534
- https://github.com/nasa/fprime/releases/tag/v4.2.0
- https://github.com/nasa/fprime/security/advisories/GHSA-vfwv-3qv7-jjjq
- https://github.com/nasa/fprime/security/advisories/GHSA-vfwv-3qv7-jjjq