CVE-2026-32743 affects PX4 Autopilot versions 1.17.0-rc2 and earlier. The vulnerability is a stack-based buffer overflow in the MavlinkLogHandler logic that processes log list entries. Specifically, the LogEntry.filepath buffer is 60 bytes, but sscanf parses file paths from the log list file without a width specifier, allowing an overlong path to overflow the stack buffer. According to the provided description, an attacker with MAVLink link access can prepare the condition by creating deeply nested directories via MAVLink FTP and then trigger the vulnerable code path by issuing a MAVLink log request for the log list.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.