Skip to main content

F Prime EUVDEUVD-2026-101408

| CVE-2026-92156 MEDIUM
Incorrect Calculation of Buffer Size (CWE-131)
2026-10-14 GitHub_M
6.5
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

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

  1. Access
    Gain adjacent-bus/bridged-component access
  2. Delivery
    Craft maximum-size legal Fw::LogBuffer
  3. Exploit
    Forward event via GenericHub to EventManager
  4. Execution
    Serialization exceeds ComBuffer budget
  5. Impact
    FW_ASSERT aborts/resets process (DoS)

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Buffer size calculation
Exploitation Conditions

Exploitation requires a deployment that bridges events across address spaces through Svc::GenericHub into Svc::EventManager (the loqQueue_internalInterfaceHandler path) and forwards a legal Fw::LogBuffer whose size approaches the framework LogBuffer maximum. The trigger is that event metadata (packet descriptor, event identifier, time-tag) consumes part of the ComBuffer, leaving a smaller remaining budget for log arguments, so a maximum-size legal payload overflows that budget and fails serialization, reaching the standard F Prime FW_ASSERT. Limiting factors: this is NOT remotely exploitable against a default standalone configuration - it specifically depends on the GenericHub event-bridging topology (AV:A adjacent access), affects only fprime versions before 4.3.0, and under non-default assertion handling (if assertions are configured not to abort) the practical impact changes. Impact is limited to availability (process abort/reset); no code execution or data exposure.

Impact

This is a genuine but bounded availability issue, not a top-tier emergency. The CVSS 3.1 vector (AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 6.5) indicates adjacent-network, low-complexity, unauthenticated impact limited purely to availability - consistent with CWE-131 (incorrect buffer size calculation) and the described assertion-driven abort/reset. There is no confidentiality or integrity impact and no scope change, so this cannot be chained into code execution or data theft from the data provided. No EPSS score, SSVC decision, KEV listing, or POC was supplied: exploitation status is therefore 'no public exploit identified at time of analysis,' and the absence of KEV/EPSS means there is no evidence of active or widespread exploitation. The AV:A rating is defensible because the vulnerable path specifically requires a GenericHub bridge from another address space rather than arbitrary internet reach, which materially narrows the realistic attacker population to those already on or adjacent to the spacecraft/embedded bus. Real-world priority is MODERATE and situational: it only matters for F Prime deployments that actually bridge events cross-domain via GenericHub, and the worst case is a process abort/reset (a DoS) on an embedded flight or avionics system where a reset can still be operationally significant.

Exploit ScenarioDerived

In an F Prime deployment where events are bridged across address spaces through GenericHub into Svc::EventManager, an attacker (or a misbehaving bridged component) on the adjacent bus forwards a legal maximum-size Fw::LogBuffer whose log arguments exceed EventManager's remaining ComBuffer budget after packet-descriptor, event-ID, and time-tag metadata. Serialization then fails and reaches the standard F Prime FW_ASSERT, aborting or resetting the process and causing denial of service. No public proof-of-concept was provided, but the fixed PR diff and advisory precisely describe the triggering condition.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.5% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 14, 2026

Denial of service through process abort and reset in NASA's F´ (F Prime) framework affects all versions prior to 4.3.0 when a deployment bridges events across address spaces via Svc::GenericHub into Svc::EventManager. A legal Fw::LogBuffer whose size approaches the framework LogBuffer maximum leaves insufficient room in the destination ComBuffer once the packet descriptor, event identifier, and time-tag metadata are serialized, so serialization returns a failure status that reaches the standard F Prime FW_ASSERT and terminates the process. The flaw is adjacent-network reachable (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 6.5), requires no privileges, and yields availability impact only; no public exploit code was identified at time of analysis, and the vendor-released fix is version 4.3.0.

RemediationAI

Upgrade to F´ (F Prime) 4.3.0, which is the vendor-released fix (release tag https://github.com/nasa/fprime/releases/tag/v4.3.0, corresponding to GitHub PR https://github.com/nasa/fprime/pull/5633 and commit https://github.com/nasa/fprime/commit/7eacd551aaf6d9a21e347ac2c8d827ca15ee5755); the change replaces the FW_ASSERT on serialization status in EventManager::loqQueue_internalInterfaceHandler with a logged drop-and-return, and enlarges GenericHub's outgoing buffer from Fw::ComBuffer::SERIALIZED_SIZE to FW_COM_BUFFER_MAX_SIZE + sizeof(U32). Details are in the upstream advisory at https://github.com/nasa/fprime/security/advisories/GHSA-6fxx-mgfv-55g7. If upgrading is not immediately possible, backport the two-line EventManager change so a failed serialization logs and drops the event instead of aborting, and widen the GenericHub buffer allocation if maximum-size payloads must round-trip. A compensating control is to avoid bridging event traffic through GenericHub into EventManager, or to constrain event argument sizes on bridged events below the maximum LogBuffer size so the combined metadata plus arguments fit the ComBuffer, though this requires auditing every event definition in the deployment and will silently truncate or drop oversized events if misconfigured. Changing assertion handling so that FW_ASSERT does not abort reduces the immediate reset but trades away the safety net that assertions provide for other fault classes and is not recommended as a standalone mitigation.

Affected VersionsENISA

fprime < 4.3.0

Affected Packages

euvd fprime fix: 4.3.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, built around typed ports, components, and fixed-capacity serialization buffers. This issue is classified as CWE-131 (Incorrect Calculation of Buffer Size). EventManager::loqQueue_internalInterfaceHandler receives events on its internal queue interface and serializes them into an Fw::ComBuffer; the buffer must hold not only the raw log arguments but also a packet descriptor, the event identifier, and a time-tag, and each event's arguments can legally be as large as the framework's Fw::LogBuffer maximum. The size budget was therefore computed against the wrong bound: a maximum-size LogBuffer is legal on its own but is illegal once the surrounding event metadata is added inside the smaller remaining ComBuffer space, and the serializer returns FW_SERIALIZE_NO_ROOM_LEFT rather than succeeding. Because the pre-fix code wrapped the serialization result in FW_ASSERT(Fw::FW_SERIALIZE_OK == stat), the mismatch between the Legal LogBuffer maximum and the actual post-metadata budget turns a valid bridged payload into a fatal assertion. The bridging path through Svc::GenericHub is what makes the payload attacker-influenceable, since it forwards events originating in another address space; GenericHub's own outgoing stack buffer was also sized only as Fw::ComBuffer::SERIALIZED_SIZE, which the fix widens to FW_COM_BUFFER_MAX_SIZE + sizeof(U32) to accommodate a maximum-size serialized command/event payload plus the context word. The net effect of the defect class is a fatal assertion rather than memory corruption, memory disclosure, or code execution.

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 6.5 MEDIUM
AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI 6.5 MEDIUM

Adjacent bridged-bus delivery (AV:A), no auth on the bridged event path (PR:N), low complexity once the hub bridge exists (AC:L), and availability-only abort/reset (C:N/I:N/A:H).

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

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

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

Lifecycle Timeline

1
Patch available
Oct 14, 2026 - 18:05 EUVD

DescriptionCVE.org

F´ (F Prime) is a framework that enables development and deployment of spaceflight and other embedded software applications. Prior to 4.3.0, Svc::EventManager loqQueue_internalInterfaceHandler packetization is vulnerable because EventManager accepts up to the framework LogBuffer maximum, but packet descriptor, event identifier, and time-tag metadata consume part of the larger ComBuffer and leave a smaller remaining budget for log arguments; serialization failure then reaches an assertion. When a deployment bridges events through GenericHub into EventManager and forwards a legal Fw::LogBuffer larger than EventManager remaining log-argument budget, under standard F Prime assertion handling, a legal bridged event payload aborts or resets the process, causing denial of service. This issue is fixed in version 4.3.0.

Threat Intelligence Overview

EPSS Score
0.5%
Top 56% exploitable
Prevalence
Low
niche NASA spaceflight/embedded framework, limited specialized deployment footprint
Data Quality
6 sources
Confidence: High

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.5%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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
Poc
System Exposure· derived
Controlled
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

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

Attack Technique

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-92158 HIGH
7.2 Oct 14

Memory corruption in NASA's F´ (F Prime) FpySequencer component, affecting framework versions prior to 4.2.0, lets an au

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-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