Loading vulnerability…
CVE-2025-5640 is a stack-based buffer overflow in PX4-Autopilot 1.12.3. The flaw is reported in the function MavlinkReceiver::handle_message_trajectory_representation_waypoints within mavlink_receiver.cpp, specifically in the handler for the MAVLink TRAJECTORY_REPRESENTATION_WAYPOINTS message. A crafted message can trigger improper bounds handling during processing, resulting in a stack-based overwrite condition. The available information classifies the issue as requiring local access and indicates that public exploit details exist.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a proof-of-concept exploit for CVE-2025-5640, a stack-based buffer overflow vulnerability in PX4 Military UAV Autopilot versions <=1.12.3. The exploit is implemented in Python (CVE-2025-5640.py) and uses the pymavlink library to send a specially crafted MAVLink message (TRAJECTORY_REPRESENTATION_WAYPOINTS) over UDP to the target autopilot. The default target is localhost (127.0.0.1) on UDP port 14540, but both IP and port can be specified via command-line arguments. The exploit can operate in two modes: 'dos' (sends the exploit packet to crash the autopilot) and 'check' (tests connectivity to the target). The README provides usage instructions, requirements, and a disclaimer. The LICENSE file contains the GNU Affero General Public License. The exploit demonstrates a denial-of-service condition and is intended for research and educational purposes only.
9 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.