{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32707 exists.","fix":"No fix has been published for CVE-2026-32707 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32707 is a medium-severity memory corruption vulnerability in PX4-Autopilot, published on 13 Mar 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-32707 and fix it if it is affected.\n\nWhat it is: CVE-2026-32707 is a medium-severity memory corruption vulnerability in PX4-Autopilot, published on 13 Mar 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-32707 exists.\n\nAffected product: PX4-Autopilot. 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-32707/ (Markdown: https://insights.sbomify.com/CVE-2026-32707/index.md)","id":"CVE-2026-32707","markdown":"https://insights.sbomify.com/CVE-2026-32707/index.md","name":"CVE-2026-32707","record":{"aliases":["GHSA-wxwm-xmx9-hr32"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Drone autopilot firmware","requires_auth":"none","summary":"Attacker with CAN access can cause stack buffer overflow in PX4 autopilot, leading to crashes or potential code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"px4_drone_autopilot","vendor":"dronecode"}],"cvss":{"score":5.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"PX4 autopilot is a flight control solution for drones. Prior to 1.17.0-rc2, tattu_can contains an unbounded memcpy in its multi-frame assembly loop, allowing stack memory overwrite when crafted CAN frames are processed. In deployments where tattu_can is enabled and running, a CAN-injection-capable attacker can trigger a crash (DoS) and memory corruption. This vulnerability is fixed in 1.17.0-rc2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-05-08","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-05-08T11:12:14Z","kind":"github_poc","ref":"https://github.com/mbanyamer/CVE-2026-32707-PX4-Autopilot-tattu_can-Stack-Buffer-Overflow-DoS-","stars":0,"title":"CVE-2026-32707 PX4-Autopilot tattu_can Stack Buffer Overflow (DoS) Exploit Tool"}],"tier":"weaponised"},"has_fix":false,"headline":"PX4 autopilot has a stack buffer overflow in tattu_can due to unbounded memcpy in frame assembly loop","id":"CVE-2026-32707","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Zenoh uORB Subscriber Allows Arbitrary Stack Allocation (PX4/PX4-Autopilot)","id":"CVE-2026-32708"},"packages":[],"prev":{"headline":"PX4 autopilot has a global buffer overflow in crsf_rc via oversized variable-length known packet","id":"CVE-2026-32706"},"products":["PX4-Autopilot"],"published":"2026-03-13","related":[{"cvss_score":8.1,"headline":"Business logic in n/a","id":"CVE-2026-26741","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":8.1,"headline":"Security feature bypass in n/a","id":"CVE-2026-26742","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":7.9,"headline":"Memory corruption in n/a","id":"CVE-2024-40427","kev_date_added":null,"published":"2025-01-07"},{"cvss_score":7.8,"headline":"Zenoh uORB Subscriber Allows Arbitrary Stack Allocation (PX4/PX4-Autopilot)","id":"CVE-2026-32708","kev_date_added":null,"published":"2026-03-13"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2024-38952","kev_date_added":null,"published":"2024-06-25"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2021-46896","kev_date_added":null,"published":"2023-07-06"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2021-34125","kev_date_added":null,"published":"2023-03-09"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-17","vendors":["PX4"]},"summary":"Attacker with CAN access can cause stack buffer overflow in PX4 autopilot, leading to crashes or potential code execution.","url":"https://insights.sbomify.com/CVE-2026-32707/"}