{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92158 exists.","fix":"No fix has been published for CVE-2026-92158 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92158 is a high-severity vulnerability in nasa fprime, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-92158 and fix it if it is affected.\n\nWhat it is: CVE-2026-92158 is a high-severity vulnerability in nasa fprime, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92158 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-92158/ (Markdown: https://insights.sbomify.com/CVE-2026-92158/index.md)","id":"CVE-2026-92158","markdown":"https://insights.sbomify.com/CVE-2026-92158/index.md","name":"CVE-2026-92158","record":{"aliases":["GHSA-vfwv-3qv7-jjjq"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"F Prime framework","requires_auth":"high_privilege","summary":"Integer overflow in F Prime sequencer allows out-of-bounds writes, potentially leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","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 4.2.0, Svc::FpySequencer STORE directive stack write validation the bounds check adds attacker-controlled offset and size before memcpy, allowing integer wraparound to make an out-of-range destination appear valid. When a sequence-controlled STORE directive supplies a stack offset and size whose U32 sum wraps, memcpy can write outside the sequencer stack, causing memory corruption, denial of service, and potentially code execution. This issue is fixed in version 4.2.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´: FpySequencer Integer Overflow in Stack Offset/Size Validation Leading to Out-of-Bounds Write","id":"CVE-2026-92158","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"F´: TlmPacketizer copies oversized telemetry past configured channel slots and emits corrupted packetized telemetry","id":"CVE-2026-92159"},"packages":[],"prev":{"headline":"F´: FileDownlink SendPartial integer overflow lets legal startOffset/length values reach a reachable assertion","id":"CVE-2026-92157"},"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":"total"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["nasa"]},"summary":"Integer overflow in F Prime sequencer allows out-of-bounds writes, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2026-92158/"}