{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92159 exists.","fix":"No fix has been published for CVE-2026-92159 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92159 is a medium-severity memory corruption 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-92159 and fix it if it is affected.\n\nWhat it is: CVE-2026-92159 is a medium-severity memory corruption 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-92159 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-92159/ (Markdown: https://insights.sbomify.com/CVE-2026-92159/index.md)","id":"CVE-2026-92159","markdown":"https://insights.sbomify.com/CVE-2026-92159/index.md","name":"CVE-2026-92159","record":{"aliases":["GHSA-grrq-8rmr-xf83"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"F Prime framework","requires_auth":"none","summary":"Attackers can cause memory corruption and emit corrupted telemetry by sending oversized values to fixed-size channels in the F Prime framework.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-805","name":"Buffer Access with Incorrect Length Value"},{"id":"CWE-130","name":"Improper Handling of Length Parameter Inconsistency"}],"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::TlmPacketizer TlmRecv_handler fixed-slot copy TlmRecv_handler copies val.getSize bytes into entry.channelSize storage without confirming that the runtime value fits. When a telemetry update for a configured channel carries a serialized value larger than that channel fixed slot, the copy overwrites adjacent channel fields and causes corrupted packetized telemetry to be emitted. 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´: TlmPacketizer copies oversized telemetry past configured channel slots and emits corrupted packetized telemetry","id":"CVE-2026-92159","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"F´: SendPartial Integer Overflow Leading to Assertion DoS","id":"CVE-2026-92160"},"packages":[],"prev":{"headline":"F´: FpySequencer Integer Overflow in Stack Offset/Size Validation Leading to Out-of-Bounds Write","id":"CVE-2026-92158"},"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-15","vendors":["nasa"]},"summary":"Attackers can cause memory corruption and emit corrupted telemetry by sending oversized values to fixed-size channels in the F Prime framework.","url":"https://insights.sbomify.com/CVE-2026-92159/"}