CVE-2026-94127
F5 BIG-IP APM Heap-based Buffer Overflow Vulnerability
Description
CVE-2026-94127 is a critical heap-based buffer overflow in F5 BIG-IP Access Policy Manager (APM) that allows an unauthenticated attacker to achieve remote code execution. The vulnerability is reached when a BIG-IP APM access policy and an OAuth profile are configured on a virtual server, and it exists only where APM acts as an OAuth Authorization Server; deployments using APM strictly as an OAuth Client or Resource Server, without authorization server profiles, are not affected. F5 notes that BIG-IP systems in Appliance mode are also vulnerable, and that this is a data plane issue with no control plane exposure. CISA has added CVE-2026-94127 to the Known Exploited Vulnerabilities catalog, its EPSS score of 2.2% places it in the 82nd percentile, and its remediation deadline of September 25, 2026 has already passed.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HOpen in CalculatorAffected Products
| Vendor | Product | Version |
|---|---|---|
| f5 | big-ip access policy manager | >= 17.0.0, <= 17.1.3; >= 17.5.0, <= 17.5.1; 21.1.0 |
References
- https://my.f5.com/manage/s/article/K000162605(Vendor Advisory)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-94127(US Government Resource)
Weakness Type
CWE-122: Heap-based Buffer Overflow
A heap-based buffer overflow occurs when a program writes more data into a dynamically allocated buffer than it can hold, corrupting adjacent heap objects and allocator metadata. In BIG-IP APM's OAuth authorization server handling, specific malicious traffic drives such a write, and corrupting heap structures — chunk headers, free lists, object pointers — is the mechanism that lets an attacker steer execution and ultimately run code on the device.
Learn more: CWE-122 — Heap-based Buffer Overflow
Impact Analysis
CVE-2026-94127 has a CVSS 3.1 base score of 9.8 (Critical) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Attack Vector (Network), Privileges Required (None), User Interaction (None), Attack Complexity (Low): specific malicious traffic to the virtual server is the whole attack — no credentials, no victim, and the Low complexity rating is notable for a heap overflow, indicating that exploitation does not depend on winning a race or an improbable memory layout. Confidentiality, Integrity and Availability (all High): code execution on a BIG-IP APM exposes the authentication traffic it terminates, the OAuth tokens and session material it issues, and the configuration and certificates of the access policies; it allows altering who is granted access to the applications behind it, and it allows taking that access away entirely. The configuration dependency is the one limiting factor and deserves precise reading: only APM acting as an OAuth Authorization Server is affected, so the first remediation step is determining which virtual servers carry such a profile. F5 confirms that Appliance mode does not protect against this. With a lapsed KEV deadline, an exposed and matching configuration should be treated as compromised.
Exploit Maturity
CISA has added CVE-2026-94127 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, and the remediation deadline of September 25, 2026 has already passed; the entry does not flag use in ransomware campaigns. The references are the F5 security article K000162605 and the CISA catalog entry rather than exploit code, so no public proof-of-concept is listed. The EPSS score of 2.2% places the vulnerability in the 82nd percentile, well above the median and high for a memory corruption flaw — consistent with the Low attack complexity rating, which signals a bug that does not require exotic exploitation skill. F5 BIG-IP devices sit at the front of enterprise and government application estates and have been a recurring target for well-resourced intrusion sets; a reliably exploitable unauthenticated overflow in the access policy data plane is exactly the kind of capability such actors retain and reuse. Identify affected virtual servers today and treat any that were exposed as requiring forensic review.
Remediation
- Carry out the action CISA requires, immediately. Apply mitigations in accordance with F5's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV remediation deadline of September 25, 2026 has already passed.
- Determine your exposure before anything else. Check each virtual server for the combination of a BIG-IP APM access policy and an OAuth profile, and specifically for OAuth Authorization Server profiles. Deployments using APM only as an OAuth Client or Resource Server are not affected, which may narrow the work considerably — but the check must be done per virtual server, not per device.
- Upgrade BIG-IP APM to a fixed release. The affected ranges are 17.0.0 through 17.1.3, 17.5.0 through 17.5.1 and 21.1.0; the fixed versions and any temporary mitigations are documented in F5 article K000162605. Note F5's caveat that versions past End of Technical Support were not evaluated — those need migration to a supported branch.
- Reduce reachability of the affected virtual servers in the interim. This is a data plane issue, so the exposure is the published service itself rather than the management interface; where the business allows, restrict source networks for the affected virtual servers, or temporarily remove the OAuth authorization server profile until the upgrade is complete.
- Investigate, then harden. Look for unexplained TMM restarts and crash dumps, which are the visible side effect of an unreliable heap overflow attempt, check the device for unexpected files, iRules, scheduled tasks and user accounts, compare the configuration against a known-good copy, and rotate the signing keys and certificates used for OAuth token issuance along with any credentials the access policies hold — code execution on the data plane means all of that may be known to the attacker.
Technical Details
When a BIG-IP APM access policy and an OAuth profile are attached to a virtual server and APM is configured as an OAuth Authorization Server, specific malicious traffic reaches a code path that writes beyond the bounds of a heap-allocated buffer. Heap overflows corrupt whatever is adjacent — other allocated objects, chunk headers, free list pointers — and modern exploitation turns that corruption into control over a function pointer or allocator behaviour, which is how CWE-122 becomes remote code execution rather than only a crash. The CVSS rating of Low attack complexity is the telling detail: it indicates the memory layout at the point of overflow is predictable enough that an attacker does not need favourable conditions. F5's scoping statements narrow the affected population precisely — only the authorization server role is vulnerable, Client and Resource Server roles are not — while widening the concern in one respect, since Appliance mode, which restricts administrative access to the underlying system, provides no protection here. The vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H records an unchanged scope, with the compromised authority being the BIG-IP itself.
Frequently Asked Questions
Is CVE-2026-94127 being actively exploited?
Yes. CISA has added CVE-2026-94127 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, and the remediation deadline of September 25, 2026 has already passed. Use in ransomware campaigns is not recorded, and the EPSS score of 2.2% places the vulnerability in the 82nd percentile for exploitation likelihood.
What products are affected by CVE-2026-94127?
CVE-2026-94127 affects F5 BIG-IP Access Policy Manager in versions 17.0.0 through 17.1.3, 17.5.0 through 17.5.1 and 21.1.0, but only where a virtual server has both an APM access policy and an OAuth profile and APM is configured as an OAuth Authorization Server. Deployments using APM strictly as an OAuth Client or Resource Server are not affected. BIG-IP systems in Appliance mode are vulnerable as well.
How do I fix CVE-2026-94127?
First identify which virtual servers combine an APM access policy with an OAuth Authorization Server profile, then upgrade BIG-IP APM to the fixed release for your branch per F5 article K000162605; versions past End of Technical Support need migration instead. As an interim step, restrict source networks for the affected virtual servers or remove the OAuth authorization server profile, and afterwards rotate OAuth signing keys and certificates.
How severe is CVE-2026-94127?
CVE-2026-94127 is rated Critical with a CVSS 3.1 base score of 9.8: unauthenticated remote code execution over the network with no user interaction and full impact on confidentiality, integrity and availability. Its EPSS score of 2.2% sits in the 82nd percentile. Severity for a given organization depends entirely on configuration — only APM as an OAuth Authorization Server is affected — but where that configuration exists, the device is the access gatekeeper and the impact is correspondingly broad.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.