CVE-2026-92158

Deferred Deferred - Pending Action

Stack Memory Corruption in F Prime Framework

Publication date: 2026-10-14

Last updated on: 2026-10-14

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-14

Last Modified

2026-10-14

Generated

2026-10-19

AI Q&A

2026-10-15

EPSS Evaluated

2026-10-18

NVD

CVE-2026-92158

EUVD

EUVD-2026-101411

Affected Vendors & Products

Vendor	Product	Version / Range
nasa	fprime	< 4.2.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-190	The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
CWE-787	The product writes data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

Executive Summary

CVE-2026-92158 is a high-severity vulnerability in the FpySequencer component of the NASA F Prime framework. It involves an integer overflow in stack offset and size validation within the STORE directive handler. Attackers can craft a directive where the sum of offset and size wraps around due to 32-bit unsigned integer limits, bypassing bounds checks. This allows memcpy to write outside the allocated stack memory, causing memory corruption, denial of service, and potential code execution.

Detection Guidance

Detecting this vulnerability requires checking the F Prime framework version and analyzing the FpySequencer component for integer overflow issues in STORE directive handling. Inspect the framework version to ensure it is 4.2.0 or later. Review the FpySequencer implementation for bounds checks on stack offsets and sizes, particularly focusing on U32 integer overflows during memcpy operations.

Impact Analysis

This vulnerability can lead to memory corruption, system crashes, or arbitrary code execution depending on build flags and memory layout. It may cause denial-of-service attacks by crashing applications using vulnerable versions of F Prime before 4.2.0.

Compliance Impact

This vulnerability could lead to memory corruption and arbitrary code execution, which may result in unauthorized access to sensitive data. For GDPR, this could violate principles of data protection and confidentiality. For HIPAA, it might compromise protected health information integrity and availability.

Mitigation Strategies

Upgrade F Prime to version 4.2.0 or later to address the integer overflow in the STORE directive stack validation. Review and test all sequence-controlled STORE directives for potential out-of-bounds writes. Monitor for memory corruption or denial-of-service events as potential indicators of exploitation.

Hi! I’m here to help you understand CVE-2026-92158. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70