# CVE-2026-94127: F5 BIG-IP APM Heap-based Buffer Overflow

> Unauthenticated attackers can achieve remote code execution on BIG-IP systems configured as OAuth Authorization Servers via malicious traffic.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Yes, since 22 Sep 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-qppv-6jrg-hxq4

## What is CVE-2026-94127?

CVE-2026-94127 is a critical memory corruption vulnerability in F5 Big-Ip Access Policy Manager, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When a BIG-IP APM access policy and an OAuth profile are configured on a virtual server, specific malicious traffic can lead to remote code execution (RCE). This vulnerability is only present when BIG-IP APM is configured as an OAuth Authorization Server. Deployments using APM strictly as an OAuth Client / Resource Server (without OAuth authorization server profiles configured) are not affected by this vulnerability.

Impact:
This vulnerability allows an unauthenticated attacker to perform remote code execution. The BIG-IP system in Appliance mode is also vulnerable. This is a data plane issue; there is no control plane exposure.

 

Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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

It affects 1 product.


Products: F5 Big-Ip Access Policy Manager.

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

No fix has been published for CVE-2026-94127 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 25 Sep 2026.

## Is CVE-2026-94127 being exploited?

Yes. Attackers have exploited CVE-2026-94127 in the wild since at least 22 Sep 2026.

Public exploit code:

- https://github.com/watchtowrlabs/watchTowr-vs-f5-bigip-PreAuth-RCE-CVE-2026-94127 (github_poc): https://github.com/watchtowrlabs/watchTowr-vs-f5-bigip-PreAuth-RCE-CVE-2026-94127
- CVE-2026-94127 (github_poc): https://github.com/FurkanKAYAPINAR/CVE-2026-94127

## Other vulnerabilities in F5 Big-Ip Access Policy Manager

- [CVE-2023-46747](https://insights.sbomify.com/CVE-2023-46747/): F5 BIG-IP Configuration Utility Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2022-1388](https://insights.sbomify.com/CVE-2022-1388/): F5 BIG-IP Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2021-22986](https://insights.sbomify.com/CVE-2021-22986/): F5 BIG-IP and BIG-IQ Centralized Management iControl REST Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2021-22991](https://insights.sbomify.com/CVE-2021-22991/): F5 BIG-IP Traffic Management Microkernel Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2020-5902](https://insights.sbomify.com/CVE-2020-5902/): F5 BIG-IP Traffic Management User Interface (TMUI) Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94127 is a critical memory corruption vulnerability in F5 Big-Ip Access Policy Manager, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-94127 in the wild since at least 22 Sep 2026.

Affected product: F5 Big-Ip Access Policy Manager. 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-94127/ (Markdown: https://insights.sbomify.com/CVE-2026-94127/index.md)
```

## Sources

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

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