Ad · Leaderboard 728×90

CVE-2026-92152

9.3Critical

Published 14 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

9.3Critical
Attack vector
Network
Complexity
Low
Privileges needed
None
User interaction
None
Impact
Full C/I/A compromise
Weakness
CWE-129

Impact

Remote, unauthenticated attackers can crash the application or achieve remote code execution via malformed packets. This requires network access to a system running F Prime's Svc::GenericHub.

Root cause

The Svc::GenericHub output-port dispatcher uses deserialized port indices without validating array bounds, causing an assertion failure or out-of-bounds heap memory access.

Affected systems

F Prime versions 4.1.0 up to (excluding) 4.2.0

CVSS v4.0 · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Fix & remediation

Upgrade the F Prime framework dependency to version 4.2.0. If immediate patching is not possible, restrict network access to Svc::GenericHub ports or disable the hub component.

shell
$ git checkout v4.2.0

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-92152

Ad · Sticky 320×50 / 728×90