{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32724 exists.","fix":"No fix has been published for CVE-2026-32724 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32724 is a medium-severity use after free 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-32724 and fix it if it is affected.\n\nWhat it is: CVE-2026-32724 is a medium-severity use after free 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-32724 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-32724/ (Markdown: https://insights.sbomify.com/CVE-2026-32724/index.md)","id":"CVE-2026-32724","markdown":"https://insights.sbomify.com/CVE-2026-32724/index.md","name":"CVE-2026-32724","record":{"aliases":["GHSA-j5w2-w79c-mqrw"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PX4 autopilot","requires_auth":"none","summary":"A race condition in PX4 autopilot allows remote attackers to trigger a heap use-after-free via MAVLink messages, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"px4_drone_autopilot","vendor":"dronecode"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"PX4 autopilot is a flight control solution for drones. Prior to 1.17.0-rc1, a heap-use-after-free is detected in the MavlinkShell::available() function. The issue is caused by a race condition between the MAVLink receiver thread (which handles shell creation/destruction) and the telemetry sender thread (which polls the shell for available output). The issue is remotely triggerable via MAVLink SERIAL_CONTROL messages (ID 126), which can be sent by an external ground station or automated script. This vulnerability is fixed in 1.17.0-rc1.","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":"PX4 autopilot has a heap Use-After-Free in MavlinkShell::available() via SERIAL_CONTROL Race Condition","id":"CVE-2026-32724","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"SciTokens C++: Relative Path Traversal Vulnerability","id":"CVE-2026-32725"},"packages":[],"prev":{"headline":"SandboxJS timers have an execution-quota bypass (cross-sandbox currentTicks race)","id":"CVE-2026-32723"},"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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-16","vendors":["PX4"]},"summary":"A race condition in PX4 autopilot allows remote attackers to trigger a heap use-after-free via MAVLink messages, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2026-32724/"}