Skip to main content

F´ FpySequencer CVE-2026-92158

| EUVDEUVD-2026-101411 HIGH
Integer Overflow or Wraparound (CWE-190)
2026-10-14 GitHub_M
7.2
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain sequence execution privileges
  2. Delivery
    Deliver crafted STORE directive sequence
  3. Exploit
    Trigger U32 offset+size integer wraparound
  4. Execution
    memcpy writes past sequencer stack
  5. Impact
    Corrupt memory causing DoS or code execution

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires the attacker to supply and execute an F´ FpySequencer sequence containing a STORE directive whose stack offset and size, summed as U32, overflow so the destination bounds check is bypassed; this is a sequence-controlled code path, so the attacker must hold privileges to load/run sequences (PR:H - typically trusted command/uplink or ground-system authority). Affects only F´ versions prior to 4.2.0. Limiting factors: no public exploit exists, the high privilege requirement excludes unauthenticated attackers, and exploitation depends on the target actually running the FpySequencer component with the STORE directive reachable; no user interaction is required once a malicious sequence is executed.

Impact

This is a genuine but access-gated memory-corruption flaw rather than a mass-exploitation threat. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base 7.2) combines network reachability and low complexity with a HIGH privilege requirement - PR:H, meaning the attacker must already have authority to supply and run FpySequencer sequences, which on a spacecraft is a trusted command/uplink role. That privilege gate is the dominant risk-limiting factor and explains why this is High rather than Critical. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no public exploit identified at time of analysis and no evidence of active or automatable exploitation. The underlying bug (CWE-190 integer wraparound: attacker-controlled offset+size summed as U32 before the bounds check, defeating validation ahead of memcpy) is a real, root-caused out-of-bounds write confirmed by the vendor advisory and the fixing PR/commit. Net: treat as a priority to patch for anyone running F´ with less-than-fully-trusted sequence sources, but the high-privilege prerequisite and absence of exploitation signals mean it is not an internet-facing wormable emergency.

Exploit ScenarioDerived

An actor with authority to load and execute FpySequencer sequences (e.g., a compromised ground station or insider with command-uplink access) crafts a sequence containing a STORE directive whose stack offset and size sum to a value that wraps around in U32 arithmetic, so the pre-memcpy bounds check incorrectly passes. When the directive runs, memcpy writes outside the sequencer stack, corrupting adjacent memory to crash the flight software or potentially achieve code execution. No public exploit code is known; exploitation requires crafting the malicious sequence and the privilege to run it.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.7% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Memory corruption in NASA's F´ (F Prime) FpySequencer component, affecting framework versions prior to 4.2.0, lets an authenticated high-privilege actor who can load and execute flight sequences bypass the sequencer's stack write bounds check via a U32 integer wraparound in a STORE directive, so memcpy writes outside the sequencer stack and can cause denial of service, memory corruption, and potentially code execution. It is rated CVSS 3.1 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) because the malicious sequence must be supplied and run - typically requiring trusted commanding, uplink, or ground-system authority - making it an access-gated risk rather than an unauthenticated mass-exploitation threat. No public exploit has been identified at time of analysis, there is no CISA KEV entry, and the vendor released a fixed version (4.2.0).

RemediationAI

Upgrade F´ (F Prime) to version 4.2.0, which contains the corrected directive handlers and stack copy/move helpers (release: https://github.com/nasa/fprime/releases/tag/v4.2.0, fix commit 7527430d9ae7c88f3d649d376a45c866b0aed595, PR https://github.com/nasa/fprime/pull/4534, advisory https://github.com/nasa/fprime/security/advisories/GHSA-vfwv-3qv7-jjjq) - vendor-released patch: 4.2.0. Where immediate upgrade is not possible, the effective compensating control is to restrict and audit who can load or execute Fpy sequences, since exploitation requires sequence-loading authority (PR:H): tightly gate sequence upload/uplink paths to trusted operators and existing authenticated command channels, and monitor those channels for unexpected sequences, accepting the residual risk that a compromised privileged operator can still trigger the flaw. As an additional layer, statically validate or reject any sequence whose STORE offset plus size exceeds the sequencer stack size before execution to catch the U32-wrapping condition, though this requires custom tooling and side-tooling outside the framework; disabling or excluding the FpySequencer component entirely where sequence execution is not needed removes the attack surface at the cost of losing sequence-driven behavior. Finally, watch for sequencer crashes or memory-fault telemetry as an indicator of attempted exploitation, noting that such detection is reactive rather than preventive.

Affected VersionsENISA

fprime < 4.2.0

Affected Packages

euvd fprime fix: 4.2.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

F´ (F Prime) is NASA's open-source framework for flight and embedded software, and Svc::FpySequencer is the component that executes Fpy sequences as a stream of directives. The vulnerable STORE directive writes sequence-controlled data to a location on the sequencer's internal stack; the pre-4.2.0 validation computed the destination bound by summing an attacker-controlled stack offset and size in 32-bit arithmetic before calling memcpy. Because that addition can wrap (CWE-190, integer overflow/wraparound), an out-of-range destination can pass the bounds check while memcpy still writes past the end of the stack, producing memory corruption. The upstream fix in PR 4534 (commit 7527430d9ae7c88f3d649d376a45c866b0aed595, released in v4.2.0) restructures the directive set into relative and absolute load/store variants, introduces a currentFrameStart 'frame pointer' concept, and centralizes stack manipulation into copy() and move() helpers that assert both source and destination regions are in bounds and non-overlapping, eliminating the wraparound-prone check.

Know when Fprime gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.2 HIGH

Sequences can be delivered over a command link (AV:N), the wraparound is deterministic (AC:L), but loading/running sequences needs trusted command authority (PR:H); OOB write yields full C/I/A impact.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 14, 2026 - 18:05 EUVD
CVE Published
Oct 14, 2026 - 17:14 cve.org
HIGH 7.2

DescriptionCVE.org

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.

Technical POC Analysis

Source: GitHub advisory GHSA-vfwv-3qv7-jjjq (nasa/fprime).

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

A memory-corruption flaw in NASA's F´ (F Prime) flight software framework, specifically the FpySequencer component in versions before 4.2.0, could let a privileged operator who can upload and run flight sequences corrupt sequencer memory, causing loss of command sequencing, denial of service, or possible code execution on affected spacecraft or ground test systems. Exploitation requires trusted commanding or uplink authority rather than anonymous network access, so exposure is concentrated among mission operators, integrators, and partners with sequence-upload rights rather than the general internet. Leadership should care because a successful attack or accidental trigger could interrupt mission operations or disable a vehicle, and remediation is a straightforward framework upgrade.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.7%
Top 46% exploitable
Prevalence
Low
niche NASA spaceflight/embedded framework, limited to space-sector deployments
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.7%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

37
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

More in Fprime

View all
CVE-2024-55029 MEDIUM POC
6.1 Mar 25

NASA Fprime v3.4.3 was discovered to contain multiple cross-site scripting (XSS) vulnerabilities. Rated medium severity

CVE-2026-92152 CRITICAL
9.3 Oct 14

Out-of-bounds array access in the Svc::GenericHub component of NASA's F´ (F Prime) framework (4.1.0 through 4.1.x, fixed

CVE-2026-92154 HIGH
8.1 Oct 14

Integer overflow in NASA's F´ (F Prime) Svc::FileUplink component allows an operator with command-link access to bypass

CVE-2026-92151 HIGH
7.5 Oct 14

Malformed CCSDS telecommand frames cause assertion-driven denial of service in NASA's F´ (F Prime) flight-software frame

CVE-2026-92150 HIGH
7.5 Oct 14

Malformed inter-processor hub traffic can abort or reset NASA's F´ (F Prime) flight-software process in versions prior t

CVE-2026-92155 HIGH
7.5 Oct 14

Denial of service in NASA's F´ (F Prime) framework prior to 4.2.0 allows remote attackers to abort or reset the flight s

CVE-2026-92153 HIGH
7.1 Oct 14

Path traversal in F´ (F Prime) prior to 4.3.0 lets an authenticated peer on the file-uplink channel write or overwrite f

CVE-2026-92156 MEDIUM
6.5 Oct 14

Denial of service through process abort and reset in NASA's F´ (F Prime) framework affects all versions prior to 4.3.0 w

CVE-2026-92157 MEDIUM
6.5 Oct 14

Denial of service in NASA's F´ (F Prime) flight software framework prior to 4.3.0 allows an adjacent, unauthenticated at

CVE-2026-92160 MEDIUM
6.5 Oct 14

Denial of service in NASA's F´ (F Prime) flight software framework before version 4.3.0, where an integer-overflow flaw

CVE-2026-92159 MEDIUM
6.5 Oct 14

Corrupted packetized telemetry can be emitted by NASA's F´ (F Prime) flight and embedded software framework before versi

CVE-2026-41144 NONE
Apr 22

F Prime framework before version 4.2.0 allows remote code execution via integer overflow in bounds checking combined wit

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy