Quick answers
- Is CVE-2026-41144 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41144 being exploited in the wild.
- How severe is CVE-2026-41144?
- Informational severity, with a CVSS score of 0, published 22 April 2026.
- Which products and versions are affected?
- Nasa F Prime < 4.2.0.
- Is there a fix for CVE-2026-41144?
- A patch was published on 2026-03-31: Fix committed to GitHub repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41144 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-41144?
- Check whether you run Nasa F Prime or Nasa Fprime 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.
Technical details
An integer overflow vulnerability exists in the FileUplink component of the F Prime framework. The bounds check 'byteOffset + dataSize > fileSize' uses 32-bit unsigned integer addition, which can be made to wrap around to a small value by providing a large byteOffset. This bypasses the size validation check while the subsequent file write operation uses the original large offset. When combined with a lack of path sanitization in Svc/FileUplink/File.cpp, an unauthenticated network attacker can achieve arbitrary file writes at arbitrary offsets. This can be leveraged to achieve remote code execution (RCE) on the embedded target. The issue is addressed in version 4.2.0.
Affected products
- NASA F Prime (F´) < 4.2.0
Timeline
- 2026-03-31: patched: Fix committed to GitHub repository
- 2026-04-14: advisory: GitHub security advisory published
- 2026-04-22: disclosed: CVE published to NVD