# CVE-2026-86714: PX4 Autopilot through 1.17.0 Stack Buffer Over-read via netman

> Attackers can leak stack memory via a stack buffer over-read in the netman system command by supplying long interface names.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **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:** 8 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-6x78-rh4h-q7jx

## What is CVE-2026-86714?

CVE-2026-86714 is a medium-severity vulnerability in PX4-Autopilot, published on 8 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PX4 Autopilot through 1.17.0 contains a stack buffer over-read vulnerability in the netman system command that fails to validate interface name length. Attackers can supply interface names of 74 bytes or more via the -i option to read beyond buffer boundaries, leaking stack memory to console output or writing it into persistent network configuration files.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-86714 being exploited?

There is no known exploitation of CVE-2026-86714 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86714 is a medium-severity vulnerability in PX4-Autopilot, published on 8 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86714 in the wild and no public exploit code.

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-86714/ (Markdown: https://insights.sbomify.com/CVE-2026-86714/index.md)
```

## Sources

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

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