CVE-2026-41144
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedF´ (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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceF´ framework versions before 4.2.0 contain an integer overflow vulnerability in bounds checking logic where U32 addition of byteOffset + dataSize wraps around, allowing bypass with specific values (byteOffset=0xFFFFFF9C, dataSize=100). Combined with missing file path sanitization in Svc/FileUplink/File.cpp, this enables arbitrary file write at any offset, leading to remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.1.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify F´ framework installationSearch for F´ installation directories, check for fprime or fprime-community packages, or look for F´ project structures containing 'FPrime' or 'fprime' directoriesAffected if F´ framework is installed on the system
-
Determine installed F´ versionCheck version files (VERSION.txt, version.h) in the F´ installation directory, or run 'git log'/'git describe' if installed from source, or check package metadata if installed via package managerAffected if Version is 4.1.1 or any version before 4.2.0 (e.g., 4.0.x, 3.x series)
-
Check if FileUplink component is deployedInspect project deployment configuration for Svc/FileUplink component instantiation - look for FileUplink in deployment's topology, component registry, or generated configuration files (topology.cpp, component.inits, or similar)Affected if Svc/FileUplink component is instantiated in the deployed topology
-
Verify vulnerable code path existsInspect Svc/FileUplink/File.cpp source code for the bounds checking logic involving byteOffset and dataSize U32 addition - search for the pattern 'byteOffset + dataSize' or similar arithmetic in file write handling codeAffected if The vulnerable bounds check code (U32 overflow in byteOffset + dataSize) is present in the deployed Svc/FileUplink/File.cpp
System is affected if F´ version 4.1.1 or any version before 4.2.0 is installed AND the Svc/FileUplink component is deployed in the topology with the vulnerable bounds checking code present.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to F´ version 4.2.0 which contains the patch; no workarounds are available.
4.2.0
- Confirm current Fprime version by checking installation or version file
- Upgrade Fprime to version 4.2.0 or later by pulling the latest release from the official repository
- Verify the upgrade was successful by checking the new version number
- Review application functionality to ensure the upgrade did not introduce unexpected issues
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41144 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41144 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data