{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26741 exists.","fix":"No fix has been published for CVE-2026-26741 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-26741 is a high-severity vulnerability in n/a, published on 10 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-26741 and fix it if it is affected.\n\nWhat it is: CVE-2026-26741 is a high-severity vulnerability in n/a, published on 10 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-26741 exists.\n\nAffected product: n/a. 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-26741/ (Markdown: https://insights.sbomify.com/CVE-2026-26741/index.md)","id":"CVE-2026-26741","markdown":"https://insights.sbomify.com/CVE-2026-26741/index.md","name":"CVE-2026-26741","record":{"aliases":["GHSA-hwq5-3473-h97q"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["denial_of_service","other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PX4 Autopilot","requires_auth":"none","summary":"A logic flaw in PX4 Autopilot allows uncontrolled drone ascent during specific mode switches, potentially causing flyaways and property damage.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"px4_drone_autopilot","vendor":"dronecode"}],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"PX4 Autopilot versions 1.12.x through 1.15.x contain a logic flaw in the mode switching mechanism. When switching from Auto mode to Manual mode while the drone is in the \"ARMED\" state (after landing and before the automatic disarm triggered by the COM_DISARM_LAND parameter), the system lacks a throttle threshold safety check for the physical throttle stick. This flaw can directly cause the drone to lose control, experience rapid uncontrolled ascent (flyaway), and result in property damage","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":"Business logic in n/a","id":"CVE-2026-26741","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2026-26742"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2026-26740"},"products":["n/a"],"published":"2026-03-10","related":[{"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-11","vendors":["n/a"]},"summary":"A logic flaw in PX4 Autopilot allows uncontrolled drone ascent during specific mode switches, potentially causing flyaways and property damage.","url":"https://insights.sbomify.com/CVE-2026-26741/"}