{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102808 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102808 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102808 is a high-severity vulnerability in PX4-Autopilot, published on 29 Sep 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-102808 and fix it if it is affected.\n\nWhat it is: CVE-2026-102808 is a high-severity vulnerability in PX4-Autopilot, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-102808 in the wild and no public exploit code.\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-102808/ (Markdown: https://insights.sbomify.com/CVE-2026-102808/index.md)","id":"CVE-2026-102808","markdown":"https://insights.sbomify.com/CVE-2026-102808/index.md","name":"CVE-2026-102808","record":{"aliases":["GHSA-6mwg-qhjp-3hf8"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PX4 Autopilot","requires_auth":"none","summary":"Attackers with shell access can crash the flight controller by supplying invalid byte count values to the sd_stress command.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"PX4 Autopilot through 1.17.0 contains a NULL pointer dereference vulnerability in the sd_stress command where the -b byte count parameter is parsed without validation before being passed to malloc() and memset(). Attackers with shell access, including through MAVLink, can supply invalid byte count values to crash the flight controller.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"PX4 Autopilot through 1.17.0 NULL Pointer Dereference via sd_stress","id":"CVE-2026-102808","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"PX4 Autopilot through 1.17.0 Stack Exhaustion via tests file2 Command","id":"CVE-2026-102809"},"packages":[],"prev":{"headline":"OpenClaw before 2026.9.4 Authorization Bypass via MCP App Standalone Ticket","id":"CVE-2026-102807"},"products":["PX4-Autopilot"],"published":"2026-09-29","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-02","vendors":["PX4"]},"summary":"Attackers with shell access can crash the flight controller by supplying invalid byte count values to the sd_stress command.","url":"https://insights.sbomify.com/CVE-2026-102808/"}