{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-41144 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-41144 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41144 is a vulnerability in nasa fprime, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41144 and fix it if it is affected.\n\nWhat it is: CVE-2026-41144 is a vulnerability in nasa fprime, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-41144 in the wild and no public exploit code.\n\nAffected product: nasa fprime. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-41144/ (Markdown: https://insights.sbomify.com/CVE-2026-41144/index.md)","id":"CVE-2026-41144","markdown":"https://insights.sbomify.com/CVE-2026-41144/index.md","name":"CVE-2026-41144","record":{"aliases":["GHSA-qmvv-rxh4-ccqh"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"F Prime framework","requires_auth":"none","summary":"An integer overflow in F Prime allows attackers to bypass bounds checks and write arbitrary data to any file, leading to remote code execution on embedded targets.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"fprime","vendor":"nasa"}],"cvss":{"score":0,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"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 \u003e 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"F´ (F Prime) has Integer Overflow in FileUplink","id":"CVE-2026-41144","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"MinIO has an Unauthenticated Object Write via Query-String Credential Signature Bypass in Unsigned-Trailer Uploads","id":"CVE-2026-41145"},"packages":[],"prev":{"headline":"YesWiki vulnerable to authenticated SQL Injection via id_fiche in EntryManager::formatDataBeforeSave()","id":"CVE-2026-41143"},"products":["fprime"],"published":"2026-04-21","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2024-55028","kev_date_added":null,"published":"2025-03-25"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2024-55030","kev_date_added":null,"published":"2025-03-25"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-55029","kev_date_added":null,"published":"2025-03-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-22","vendors":["nasa"]},"summary":"An integer overflow in F Prime allows attackers to bypass bounds checks and write arbitrary data to any file, leading to remote code execution on embedded targets.","url":"https://insights.sbomify.com/CVE-2026-41144/"}