CVE-2024-38951: PX4-Autopilot · n/a
Affects PX4-AutopilotSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubpx4/PX4-Autopilotpkg:github/px4/PX4-AutopilotOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-38951, organizations should immediately restrict network access to PX4-Autopilot communication channels, ensuring that only trusted and authenticated devices can send MavLink messages. Employ network segmentation and strong encryption for UAV communication to prevent unauthorized message injection. Monitor UAV telemetry and logs for abnormal MavLink traffic patterns indicative of exploitation attempts. Implement rate limiting and input validation at the communication interface to detect and block malformed or suspicious messages. Until an official patch is released, consider deploying runtime protections such as memory protection mechanisms or sandboxing the autopilot software to contain crashes. Conduct thorough testing of PX4-Autopilot updates in controlled environments before deployment. Engage with the PX4 community and vendors for timely updates and patches. Additionally, develop incident response plans specific to UAV DoS scenarios to minimize operational impact.
Description
A buffer overflow in PX4-Autopilot v1.12.3 allows attackers to cause a Denial of Service (DoS) via a crafted MavLink message.