Quick answers
- Is CVE-2026-92158 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92158 being exploited in the wild.
- How severe is CVE-2026-92158?
- High severity, with a CVSS score of 7.2, published 14 October 2026.
- Which products and versions are affected?
- Nasa F Prime prior to 4.2.0.
- Is there a fix for CVE-2026-92158?
- Yes: fixed in 4.2.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92158 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-92158?
- Check whether you run Nasa F Prime at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.2.0
Technical details
The vulnerability is an integer wraparound in the bounds check of the FpySequencer STORE directive: when a sequence-controlled STORE directive supplies a stack offset and size whose sum wraps around a 32-bit integer, the validation fails to catch the out-of-range access before memcpy is called. An attacker with the ability to craft or inject sequence directives can trigger out-of-bounds memory writes, leading to heap corruption, denial of service, or code execution. The fix was introduced in F Prime 4.2.0.
Affected products
- NASA F Prime prior to 4.2.0
Timeline
- 2026-10-14: disclosed