# CVE-2026-26742: Security feature bypass in n/a

> Attackers can bypass pre-flight safety checks in PX4 Autopilot by re-arming immediately after landing, causing uncontrolled high-thrust takeoffs.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 10 Mar 2026
- **Updated:** 11 Mar 2026
- **Also known as:** GHSA-r53q-gcfw-q36c

## What is CVE-2026-26742?

CVE-2026-26742 is a high-severity vulnerability in n/a, published on 10 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PX4 Autopilot versions 1.12.x through 1.15.x contain a protection mechanism failure in the "Re-arm Grace Period" logic. The system incorrectly applies the in-air emergency re-arm logic to ground scenarios. If a pilot switches to Manual mode and re-arms within 5 seconds (default configuration) of an automatic landing, the system bypasses all pre-flight safety checks, including the throttle threshold check. This allows for an immediate high-thrust takeoff if the throttle stick is raised, leading to loss of control.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Dronecode Px4 Drone Autopilot.

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

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

## Is CVE-2026-26742 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-26741](https://insights.sbomify.com/CVE-2026-26741/): Business logic 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)
- [CVE-2021-46896](https://insights.sbomify.com/CVE-2021-46896/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-26742 is a high-severity vulnerability in n/a, published on 10 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-26742 exists.

Affected product: n/a. 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-26742/ (Markdown: https://insights.sbomify.com/CVE-2026-26742/index.md)
```

## Sources

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

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