CVE-2025-5640 PX4-Autopilot TRAJECTORY_REPRESENTATION_WAYPOINTS Message mavlink_receiver.cpp stack-based overflow

Medium 4.8 Published Updated

A stack-based buffer overflow in PX4-Autopilot allows local attackers to execute arbitrary code or cause denial of service via crafted MAVLink messages.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is CVE-2025-5640?

CVE-2025-5640 is a medium-severity memory corruption vulnerability in PX4-Autopilot, published on 5 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

A vulnerability was found in PX4-Autopilot 1.12.3. It has been classified as problematic. This affects the function MavlinkReceiver::handle_message_trajectory_representation_waypoints of the file mavlink_receiver.cpp of the component TRAJECTORY_REPRESENTATION_WAYPOINTS Message Handler. The manipulation leads to stack-based buffer overflow. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used.

Weakness: CWE-121, CWE-119

Which versions are affected by CVE-2025-5640?

How do I fix CVE-2025-5640?

No fix has been published for CVE-2025-5640 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2025-5640 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5640 exists.

Public exploit code: 1 Exploit-DB entry and 1 proofs of concept on GitHub.

Sources

Also known as GHSA-rggh-j84q-m7ww.

Is CVE-2025-5640 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free