F5 BIG-IP APM Heap-based Buffer Overflow
CVE-2026-94127 is a critical-severity heap-based buffer overflow vulnerability in BIG-IP from F5, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions Hotfix-BIGIP-21.1.0.2.0.30.22-ENG, Hotfix-BIGIP-17.5.1.9.0.160.12-ENG, Hotfix-BIGIP-17.1.3.5.0.41.14-ENG as the first without the flaw, so updating BIG-IP to one of those releases or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on September 22, 2026, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update BIG-IP to Hotfix-BIGIP-21.1.0.2.0.30.22-ENG or Hotfix-BIGIP-17.5.1.9.0.160.12-ENG or Hotfix-BIGIP-17.1.3.5.0.41.14-ENG, whichever matches your release line, or a later version.
- CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- Read the advisory on my.f5.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| F5 | BIG-IP | 21.1.0 up to, but not including, Hotfix-BIGIP-21.1.0.2.0.30.22-ENG; 17.5.0 up to, but not including, Hotfix-BIGIP-17.5.1.9.0.160.12-ENG; 17.1.0 up to, but not including, Hotfix-BIGIP-17.1.3.5.0.41.14-ENG | Hotfix-BIGIP-21.1.0.2.0.30.22-ENG, Hotfix-BIGIP-17.5.1.9.0.160.12-ENG, Hotfix-BIGIP-17.1.3.5.0.41.14-ENG |
| F5 | Big-ip Access Policy Manager | 17.0.0 through 17.1.3; 17.5.0 through 17.5.1; 21.1.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (f5.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 9.3 | Critical | CNA (f5.com) |
| CVSS 3.1 | 9.8 | Critical | CNA (f5.com) |
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Heap-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the heap.
How developers prevent this class of flaw
- Pre-design: Use a language or compiler that performs automatic bounds checking.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: active, automatable: yes, technical impact: total).
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Record last changed materially (score, affected products, status or references).
- Deadline for US federal agencies to remediate, set by CISA.
References
Advisories
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-94127US Government Resource
Our coverage
Other vulnerabilities in BIG-IP
- 8.8 High severity
- 7.5 High severity
- 8.7 High severity
- 8.7 High severity
- 7.5 High severity
- 7.5 High severity
Recent Heap-based Buffer Overflow vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 8.3 High severity
- 8.0 High severity
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.