Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach GenericHub input/driver channel
-
DeliverySend crafted hub packet with out-of-range port index
-
ExploitBypass missing output-port range check
-
ExecutionOut-of-bounds output-port array dispatch
-
ImpactCorrupt heap and potentially execute code
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Array index validation
|
| Exploitation Conditions | Requires a deployed Svc::GenericHub component (F´ 4.1.0-4.1.x) that receives hub packets from a remote or external source via fromBufferDriver, and the attacker must be able to deliver a crafted packet whose deserialized output-port field exceeds the configured output-port array bounds. The severe (heap corruption / RCE) outcome is LIMITED to builds compiled WITHOUT assertions enabled - on assert-enabled builds the same input triggers FW_ASSERT and aborts (availability impact only). Exploitation also presupposes attacker reachability to the hub's input channel/driver, which in F´ deployments is typically a mission radio link or inter-process transport rather than an open internet service. |
| Impact | The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H, 9.3 Critical) describes a remote, unauthenticated, low-complexity flaw with high confidentiality, integrity and availability impact - consistent with CWE-129 improper array index validation leading to potential RCE. However, several real-world risk signals temper this: EPSS is not provided, the vulnerability is NOT in CISA KEV (no active exploitation), and no public POC is referenced, so exploitation status is 'no public exploit identified at time of analysis.' Critically, impact is build-dependent - the description states assert-enabled builds merely abort (a DoS/availability event), while only builds compiled WITHOUT assertions suffer out-of-bounds access, heap corruption and possible RCE; the full VC:H/VI:H/VA:H outcome therefore applies only to assertion-disabled (typically flight/release) builds. No CVSS 3.1 vector was supplied (only 4.0), so 3.1-based tooling comparisons rely on this analysis's independent assessment. Net: a genuinely high-severity memory-safety flaw in a reachable network dispatch path, but real-world urgency is bounded by the narrow deployment base (NASA F´ embedded/spaceflight systems) and absence of any observed exploitation or public exploit code - prioritize for affected F´ operators, not a broad internet emergency. |
| Exploit ScenarioDerived | An attacker with access to the communication link or driver feeding a Svc::GenericHub (e.g., a radio/uplink or inter-process channel) sends a crafted hub packet whose embedded output-port index falls outside the configured output-port array. On assert-disabled flight/release builds the unchecked index is passed to serialOut_out/bufferOut_out/eventOut_out/tlmOut_out, causing an out-of-bounds array access and heap corruption that may escalate to remote code execution; on assert-enabled builds it instead aborts. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
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 in 4.2.0) lets remote, unauthenticated attackers who can deliver a crafted hub packet via fromBufferDriver supply an output-port index outside the configured port array; assert-enabled builds abort (denial of service) while builds compiled without assertions can corrupt heap memory and potentially achieve remote code execution. No public exploit code exists and no exploitation has been confirmed in the wild - exploitation presupposes attacker reachability to the hub's input channel, which in F´ deployments is typically a mission radio link or inter-process transport rather than an internet-facing service. The vendor rates this CWE-129 improper array index validation flaw CVSS 4.0 9.3 (Critical), with high confidentiality, integrity and availability impact.
RemediationAI
Upgrade to F´ 4.2.0, the vendor-released patched version (release tag https://github.com/nasa/fprime/releases/tag/v4.2.0; upstream fix in PR https://github.com/nasa/fprime/pull/4929 and commit b56b53634fd4251ae84919f22dcff829ef9e0986), which adds type, size and output-port bounds validation before dispatching to serialOut_out, bufferOut_out, eventOut_out and tlmOut_out. If the upgrade cannot be applied immediately, the single most effective compensating control is to deploy assert-enabled builds of the affected component, because FW_ASSERT aborts on the malformed port index instead of corrupting the heap - the trade-off being that any crafted packet then becomes a denial-of-service against that component. Additional measures include validating or stripping the port index at the boundary driver so it can never leave the configured output-port array, disconnecting or removing unused output ports on GenericHub instances to shrink the attack surface, and restricting reachability of fromBufferDriver so untrusted peers cannot inject hub packets at all (in F´ deployments this normally means a mission radio link or inter-process transport rather than an internet-facing service). Because the flaw is reachable from any peer able to deliver a well-formed hub packet, network-level trust assumptions alone are not a sufficient substitute for applying the 4.2.0 fix. Full details are in the vendor advisory https://github.com/nasa/fprime/security/advisories/GHSA-vv4x-5pmf-m59g.
Affected VersionsENISA
Affected Packages
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 flight-software framework for spaceflight and embedded applications; the affected component is Svc::GenericHub, a topology component that forwards serialized hub packets - a type field, a port index, a size field and a payload - between deployments over a driver such as fromBufferDriver. In versions 4.1.0 through 4.1.x the incoming buffer is deserialized into a HubType, an FwIndexType port value and a size value, and that port value is passed straight into serialOut_out, bufferOut_out, eventOut_out or tlmOut_out without being compared against the component's configured output-port count, which is the textbook CWE-129 improper validation of array index condition. The upstream fix in PR #4929 and commit b56b53634fd4251ae84919f22dcff829ef9e0986 adds a minimum-size check (returning FW_DESERIALIZE_SIZE_MISMATCH), validates the type against HUB_TYPE_MAX (returning FW_DESERIALIZE_INVALID_DATA), verifies the declared size matches the actual buffer length, and gates each dispatch behind getNum_*OutputPorts() and isConnected_*OutputPort() bounds checks (also tightening the FwBuffSizeType cast in send_data). Affected products are tracked under CPE cpe:2.3:a:nasa:fprime:*:*:*:*:*:*:*:*, and the vulnerable path is only reachable when the Svc::GenericHub instance is instantiated, wired to output ports, and exposed to attacker-supplied hub packets.
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
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Remote unauthenticated hub packet with no user interaction (AV:N/AC:L/PR:N/UI:N); heap corruption yields potential RCE giving full C:H/I:H/A:H, though worst-case impact assumes assertion-disabled builds.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
F´ (F Prime) is a framework that enables development and deployment of spaceflight and other embedded software applications. From 4.1.0 until 4.2.0, Svc::GenericHub output-port dispatch is vulnerable because the deserialized port field is passed to serialOut_out, bufferOut_out, eventOut_out, or tlmOut_out without an explicit range check. When a remote hub packet supplies a port index outside the configured output-port array, assert-enabled builds abort, while builds without assertions can access an output-port array out of bounds, corrupt heap memory, and potentially allow remote code execution. This issue is fixed in version 4.2.0.
Technical POC Analysis
CWE-129, Improper Validation of Array Index, in Svc/GenericHub/GenericHub.cpp.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
NASA's F´ (F Prime) framework versions 4.1.0 through 4.1.x contain a critical out-of-bounds array access in the Svc::GenericHub component, fixed in version 4.2.0. A remote attacker with access to the hub's input channel-typically a mission radio link or inter-process transport rather than an internet-facing service-could trigger a denial of service on assert-enabled builds or heap corruption with potential remote code execution on non-assert builds, threatening mission availability and integrity. No public exploit identified at time of analysis, but leadership should prioritize upgrading affected mission and ground-system deployments given the critical severity and potential for operational disruption.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
NASA Fprime v3.4.3 was discovered to contain multiple cross-site scripting (XSS) vulnerabilities. Rated medium severity
Integer overflow in NASA's F´ (F Prime) Svc::FileUplink component allows an operator with command-link access to bypass
Malformed CCSDS telecommand frames cause assertion-driven denial of service in NASA's F´ (F Prime) flight-software frame
Malformed inter-processor hub traffic can abort or reset NASA's F´ (F Prime) flight-software process in versions prior t
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
Memory corruption in NASA's F´ (F Prime) FpySequencer component, affecting framework versions prior to 4.2.0, lets an au
Path traversal in F´ (F Prime) prior to 4.3.0 lets an authenticated peer on the file-uplink channel write or overwrite f
Denial of service through process abort and reset in NASA's F´ (F Prime) framework affects all versions prior to 4.3.0 w
Denial of service in NASA's F´ (F Prime) flight software framework prior to 4.3.0 allows an adjacent, unauthenticated at
Denial of service in NASA's F´ (F Prime) flight software framework before version 4.3.0, where an integer-overflow flaw
Corrupted packetized telemetry can be emitted by NASA's F´ (F Prime) flight and embedded software framework before versi
F Prime framework before version 4.2.0 allows remote code execution via integer overflow in bounds checking combined wit
EUVD-2026-101406
NVD
CVE.org
EPSS
GitHub
Exploit-DB