# CVE-2026-94127: F5 BIG-IP APM, is it exploitable where you run it

Ledger entry, disclosed 22 Sep 2026, sources read 19 Nov 2026

**The short answer.** CVE-2026-94127 affects F5 BIG-IP APM and was disclosed 22 Sep 2026 with a CVSS score of 9.3. Exposure needs these conditions: APM runs 21.1.0, 17.5.x or 17.1.x without the matching hotfix; APM acts as an OAuth Authorization Server on a virtual server the attacker can reach. CISA added it to the Known Exploited Vulnerabilities catalog on 22 Sep 2026.

## What the flaw is

CVE-2026-94127 is a heap-based buffer overflow (CWE-122) in BIG-IP Access Policy Manager (APM). When an access policy and an OAuth profile are configured on a virtual server, specific malicious traffic can cause remote code execution. No authentication is needed. F5 rates it 9.3 on CVSS 4.0 (the rating used throughout this page) and 9.8 on CVSS 3.1.

The flaw is present only when APM is set up as an OAuth Authorization Server. Deployments that use APM strictly as an OAuth client or resource server, without authorization server profiles, are not affected. The problem sits in the data plane, so management interfaces are not the route in. F5 states that systems in Appliance mode are also vulnerable.

## Are you exposed: each condition and how to check it

| Condition for exposure | How to check it on your system |
| --- | --- |
| APM runs 21.1.0, 17.5.x or 17.1.x without the matching hotfix | The hotfixes are Hotfix-BIGIP-21.1.0.2.0.30.22-ENG (21.1), Hotfix-BIGIP-17.5.1.9.0.160.12-ENG (17.5) and Hotfix-BIGIP-17.1.3.5.0.41.14-ENG (17.1). On the BIG-IP run `tmsh show sys version` for the base version and build, and `tmsh show sys software status` to see installed images and hotfixes on each volume. In the GUI use System > Software Management. Compare with the versions table. Check each device in a failover pair. |
| APM acts as an OAuth Authorization Server on a virtual server the attacker can reach | An APM access policy and an OAuth profile must both be attached to the virtual server; a client-only or resource-server-only setup is not affected. List the OAuth profiles with `tmsh list apm oauth profile`; an empty result means no OAuth profile exists and F5's condition does not hold. Then run `tmsh list ltm virtual all-properties` and look for a virtual server whose profiles include both an access profile and one of those OAuth profiles. In the GUI open Access > Federation > OAuth Authorization Server, then Local Traffic > Virtual Servers > Virtual Server List and read the Access Policy and profile settings. Then note the virtual server address and port and check which self IPs and firewall rules expose it to the internet or untrusted networks. Management (control plane) access is not the route. |
| APM is licensed and provisioned | Run `tmsh list sys provision apm` and look for a level other than none, or open System > Resource Provisioning in the GUI. |

## Affected and fixed versions

| Product line | Affected builds | First fixed build |
| --- | --- | --- |
| BIG-IP APM 21.1 | 21.1.0 up to before the hotfix | Hotfix-BIGIP-21.1.0.2.0.30.22-ENG |
| BIG-IP APM 17.5 | 17.5.0 up to before the hotfix | Hotfix-BIGIP-17.5.1.9.0.160.12-ENG |
| BIG-IP APM 17.1 | 17.1.0 up to before the hotfix | Hotfix-BIGIP-17.1.3.5.0.41.14-ENG |

F5's CVE record lists the three lines above, each as affected from the first release shown up to the named hotfix, and names no other fixed build. The affected range for 21.1 starts at 21.1.0 and ends before the hotfix whose base is 21.1.0.2. Releases 17.5.1.9 and 17.1.3.5 without the hotfix are still affected. The hotfix names carry their base releases (17.5.1.9, 17.1.3.5 and 21.1.0.2). For 17.x, install that base release first, then the hotfix, following F5's usual hotfix procedure. For 21.1 the record states no separate step for 21.1.0 or 21.1.0.1; the hotfix name carries base 21.1.0.2, so plan the same order. Versions at End of Technical Support are not evaluated, so absence from the table does not prove an older line is safe.

## If the fix cannot go in yet

- Install the hotfix for your line (versions table). It is an ENG hotfix image: install it to an inactive boot volume and reboot into it. On an HA pair, install on the standby unit first, reboot it, then fail over and repeat on the other unit. Failover drops connections that are not mirrored, and a single device is offline for the length of the reboot. This is F5's standard image-install method; K000162605 gives no separate downtime figure.
- F5 lists one workaround: an iRule, available on request by opening a ticket with F5 support. F5 does not publish the iRule or say what it changes in function, so test it on a non-production unit first.
- CISA says to apply the vendor-provided iRule as a temporary step to allow proactive forensic triage, and then install the final vendor patch as soon as possible. CISA marks forensic triage as required for this entry.
- To shrink exposure until the hotfix is in, limit which networks can reach the virtual server that carries the OAuth profile (firewall rules, or a self IP port lockdown setting). Cost: clients outside the allowed networks can no longer reach that OAuth server. This is general hardening, not a step F5 lists for this CVE.

## What to look for

- F5 and CISA publish no log strings, file paths or indicator addresses for this flaw. CISA marks forensic triage as required, so treat an internet-facing unpatched APM OAuth server as a candidate for triage under CISA's [BOD 26-04 implementation guidance](https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk).
- General checks on an APM unit you suspect (these are standard BIG-IP places to look, not indicators F5 published for this CVE): list crash files with `ls -lt /var/core`; search the traffic management log for a restart of the traffic manager with `grep -iE "tmm.*(core|SIGSEGV|restart)" /var/log/ltm`; read the APM log at `/var/log/apm` for OAuth requests from unfamiliar addresses; and compare the traffic manager's uptime with your change records using `bigstart status tmm`. A restart or a core file with no planned change on a unit that carries an OAuth Authorization Server is a reason to start forensic triage.

## Timeline

| Date | Event | Source |
| --- | --- | --- |
| 20 Sep 2026 | CVE-2026-94127 is reserved by F5. | [source](https://cveawg.mitre.org/api/cve/CVE-2026-94127) |
| 22 Sep 2026 | F5 publishes advisory K000162605 and the CVE record (public date 14:00 UTC). GitHub mirrors it as GHSA-qppv-6jrg-hxq4. F5 credits its own internal discovery. | [source](https://cveawg.mitre.org/api/cve/CVE-2026-94127) |
| 22 Sep 2026 | NVD publishes the record with F5's CVSS 4.0 score of 9.3 and CVSS 3.1 score of 9.8. | [source](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-94127) |
| 22 Sep 2026 | CISA adds the CVE to KEV with forensic triage required, ransomware use Unknown and a due date of 25 Sep 2026. The KEV note tells operators to apply the vendor-provided iRule as a temporary step, then install the final patch. | [source](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-94127) |

The earliest dated mark of exploitation is CISA's, on 22 Sep 2026, the day of disclosure; exploitation may have begun earlier.

## Exploitation reported so far

F5's advisory does not say it has seen exploitation, and no public report names the first attack, the actor or the method.

## Why static reachability settles it

Exposure turns on the build and one configuration fact: an OAuth Authorization Server profile on a virtual server that an attacker can reach. Both can be read from the BIG-IP configuration. KEV tells you attacks occurred, but only the configuration read tells you whether this device can be hit. See [static reachability](/methods/static-reachability/) for what the method proves and misses.

## Related pages

- [CVE-2026-76460: Cisco Identity Services Engine](/ledger/cve-2026-76460/)
- [CVE-2026-94545: Vercel Satori and Next.js](/ledger/cve-2026-94545/)
- [CVE-2026-81963: Microsoft Windows Update Stack](/ledger/cve-2026-81963/)

## Sources

- CVE-2026-94127: NVD record: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-94127 (read 19 Nov 2026)
- CVE-2026-94127: CISA KEV entry (feed version 2026.11.18): https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-94127 (read 19 Nov 2026)
- CVE-2026-94127: F5 advisory K000162605 (vendor advisory, as cited by the F5 CVE record): https://my.f5.com/manage/s/article/K000162605 (read 19 Nov 2026)
- CVE-2026-94127: F5 CVE record on CVE Services (vendor advisory data: affected hotfix builds, workaround): https://cveawg.mitre.org/api/cve/CVE-2026-94127 (read 19 Nov 2026)
- CVE-2026-94127: GitHub advisory GHSA-qppv-6jrg-hxq4: https://api.github.com/advisories?cve_id=CVE-2026-94127 (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://reachabilityanalysis.com/ledger/cve-2026-94127/
