# CVE-2026-32743: PX4 Autopilot: Stack-based Buffer Overflow via Oversized Path Input in MAVLink Log Request Handling

> An attacker with MAVLink access can cause a stack-based buffer overflow in PX4 Autopilot, leading to a denial of service by crashing the flight controller.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2026
- **Updated:** 19 Mar 2026
- **Also known as:** GHSA-97c4-68r9-96p5

## What is CVE-2026-32743?

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

### Official description

PX4 is an open-source autopilot stack for drones and unmanned vehicles. Versions 1.17.0-rc2 and below are vulnerable to Stack-based Buffer Overflow through the MavlinkLogHandler, and are triggered via MAVLink log request. The LogEntry.filepath buffer is 60 bytes, but the sscanf function parses paths from the log list file with no width specifier, allowing a path longer than 60 characters to overflow the buffer. An attacker with MAVLink link access can trigger this by first creating deeply nested directories via MAVLink FTP, then requesting the log list. The flight controller MAVLink task crashes, losing telemetry and command capability and causing DoS. This issue has been fixed in this commit: https://github.com/PX4/PX4-Autopilot/commit/616b25a280e229c24d5cf12a03dbf248df89c474.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-32743?

It affects 1 product.


Products: Dronecode Px4 Drone Autopilot.

## How do I fix CVE-2026-32743?

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

## Is CVE-2026-32743 being exploited?

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

Public exploit code:

- A remote Denial of Service (DoS) exploit for PX4 Autopilot versions ≤1.17.0-rc2 via a stack‑based buffer overflow in the MavlinkLogHandler. (github_poc): https://github.com/mbanyamer/CVE-2026-32743-PX4-Autopilot-MavlinkLogHandler-Stack-Buffer-Overflow-DoS-
- CVE-2026-32743 — PX4 Autopilot Stack Buffer Overflow CTT-Enhanced: 33-Layer Temporal Cascade Drone DoS .The original exploit crashes the MAVLink task via a 60-byte overflow. The CTT version distributes the overflow across 33 temporal layers, each with phase resonance timing and temporal wedge filtering.  Result: Persistent DoS. Unpatchable.  (github_poc): https://github.com/SimoesCTT/CTT-Enhanced-PX4-Autopilot-Exploit-CVE-2026-32743

## Other vulnerabilities in PX4-Autopilot

- [CVE-2026-26741](https://insights.sbomify.com/CVE-2026-26741/): Business logic in n/a (high 8.1)
- [CVE-2026-26742](https://insights.sbomify.com/CVE-2026-26742/): Security feature bypass in n/a (high 8.1)
- [CVE-2024-40427](https://insights.sbomify.com/CVE-2024-40427/): Memory corruption in n/a (high 7.9)
- [CVE-2026-32708](https://insights.sbomify.com/CVE-2026-32708/): Zenoh uORB Subscriber Allows Arbitrary Stack Allocation (PX4/PX4-Autopilot) (high 7.8)
- [CVE-2024-38952](https://insights.sbomify.com/CVE-2024-38952/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32743 and fix it if it is affected.

What it is: CVE-2026-32743 is a medium-severity memory corruption vulnerability in PX4-Autopilot, published on 18 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32743 exists.

Affected product: PX4-Autopilot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32743/ (Markdown: https://insights.sbomify.com/CVE-2026-32743/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32743
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32743
- OSV: https://osv.dev/vulnerability/CVE-2026-32743

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32743/
Summaries are generated and may contain mistakes; the official description above is the record.