CVE-2026-41144: F´ (F Prime) has Integer Overflow in FileUplink
F´ (F Prime) is a framework that enables development and deployment of spaceflight and other embedded software applications. Prior to version 4.2.0, the bounds check byteOffset + dataSize > fileSize uses U32 addition that wraps around on overflow. An attacker-crafted DataPacket with byteOffset=0xFFFFFF9C and dataSize=100 overflows to 0, bypassing the check entirely. The subsequent file write proceeds at the original ~4GB offset. Additionally, Svc/FileUplink/File.cpp:20-31 performs no sanitization on the destination file path. Combined, these allow writing arbitrary data to any file at any offset. The impact is arbitrary file write leading to remote code execution on embedded targets. Note that this is a logic bug. ASAN does not detect it because all memory accesses are within valid buffers — the corruption occurs in file I/O. Version 4.2.0 contains a patch. No known workarounds are available.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41144?
CVE-2026-41144 has been classified with a high severity due to the potential for integer overflow leading to memory corruption.
How do I fix CVE-2026-41144?
To fix CVE-2026-41144, upgrade to F Prime version 4.2.0 or later, where the integer overflow vulnerability has been addressed.
What type of vulnerability is CVE-2026-41144?
CVE-2026-41144 is categorized as an integer overflow vulnerability affecting F Prime software.
Does CVE-2026-41144 affect all versions of F Prime?
CVE-2026-41144 affects all versions of F Prime before 4.2.0.
What consequences can arise from CVE-2026-41144 if exploited?
Exploitation of CVE-2026-41144 can lead to unexpected behavior, including potential crashes or unauthorized access to system resources.