{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92157 exists.","fix":"No fix has been published for CVE-2026-92157 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92157 is a medium-severity vulnerability in nasa fprime, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-92157 and fix it if it is affected.\n\nWhat it is: CVE-2026-92157 is a medium-severity vulnerability in nasa fprime, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92157 exists.\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-92157/ (Markdown: https://insights.sbomify.com/CVE-2026-92157/index.md)","id":"CVE-2026-92157","markdown":"https://insights.sbomify.com/CVE-2026-92157/index.md","name":"CVE-2026-92157","record":{"aliases":["GHSA-hcmw-g425-8h9g"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"F Prime framework","requires_auth":"none","summary":"Integer overflow in F Prime FileDownlink allows attackers to trigger assertion failures, causing denial of service in embedded spaceflight applications.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-617","name":"Reachable Assertion"},{"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 4.3.0, Svc::FileDownlink SendPartial range validation is vulnerable because unchecked startOffset plus length arithmetic bypasses the range check and stores a wrapped m_endOffset that is inconsistent with m_byteOffset. When an existing source file is larger than a valid startOffset and a SendPartial command supplies a length whose U32 sum with that offset wraps below the file size, under standard F Prime assertion handling, the first data-packet transition reaches FW_ASSERT and aborts or resets the process, causing denial of service. This issue is fixed in version 4.3.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"F´: FileDownlink SendPartial integer overflow lets legal startOffset/length values reach a reachable assertion","id":"CVE-2026-92157","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"F´: FpySequencer Integer Overflow in Stack Offset/Size Validation Leading to Out-of-Bounds Write","id":"CVE-2026-92158"},"packages":[],"prev":{"headline":"F´: EventManager asserts on legal oversized LogBuffer values delivered over the standard GenericHub event bridge","id":"CVE-2026-92156"},"products":["fprime"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["nasa"]},"summary":"Integer overflow in F Prime FileDownlink allows attackers to trigger assertion failures, causing denial of service in embedded spaceflight applications.","url":"https://insights.sbomify.com/CVE-2026-92157/"}