TL;DR: If your BIG-IP APM is configured as an OAuth Authorization Server, apply F5's vendor-issued mitigations immediately in line with CISA's BOD 26-04 guidance. Deployments using APM only as an OAuth Client or Resource Server are not affected.
What Is the Vulnerability?
CVE-2026-94127 is a heap-based buffer overflow (CWE-122) in F5 BIG-IP Access Policy Manager (APM). The flaw is triggered when a virtual server has both a BIG-IP APM access policy and an OAuth profile configured, and the system is acting specifically as an OAuth Authorization Server. When those conditions are met, an attacker can send specially crafted, malicious traffic to the data plane that overflows the heap and leads to remote code execution (RCE).
The vulnerability is classified Critical under CVSS 3.1 with a score of 9.8 and the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. This means exploitation requires no authentication, no user interaction, no special privileges, and can be performed over the network under low-complexity conditions — the worst possible combination for defenders.
Key scoping detail from F5: this is a data plane issue; there is no control plane exposure. The management interface is not the attack surface here — it is the traffic-facing virtual server itself.
Who and What Is Affected?
The affected product is F5 BIG-IP APM. Exposure depends entirely on how APM is deployed:
- Affected: Virtual servers where BIG-IP APM is configured as an OAuth Authorization Server with both an access policy and an OAuth profile attached.
- Also affected: BIG-IP systems running in Appliance mode under the same configuration.
- Not affected: Deployments where APM is used exclusively as an OAuth Client or Resource Server — without OAuth Authorization Server profiles configured — are explicitly not vulnerable.
F5 notes that software versions that have reached End of Technical Support (EoTS) are not evaluated. Organizations running EoTS versions should treat themselves as potentially exposed and prioritize upgrading or isolating those systems.
What Is the Impact?
Successful exploitation grants an unauthenticated attacker full remote code execution on the BIG-IP APM system. The CVSS scores reflect a complete compromise across all three security pillars:
| Dimension | Rating | Meaning |
|---|---|---|
| Confidentiality | High | All data accessible to the process can be read |
| Integrity | High | Attacker can write, alter, or corrupt data and configuration |
| Availability | High | Attacker can crash or render the system unavailable |
Because BIG-IP APM systems frequently act as network gatekeepers — enforcing access control, handling authentication tokens, and brokering identity flows — full compromise of the appliance can expose downstream applications, session tokens, and user credentials that traverse the device.
CISA has added this CVE to the Known Exploited Vulnerabilities (KEV) catalog (added 2026-09-22), which indicates that exploitation in real-world environments has been confirmed at a level sufficient to warrant mandatory action under federal guidance.
What Should You Do Right Now?
CISA's required action for this vulnerability is:
"Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA's Forensics Triage Requirements. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable."
In practical terms, your immediate steps should be:
- Determine exposure: Audit every virtual server in your environment. Identify any that have an APM access policy and an OAuth Authorization Server profile active simultaneously.
- Apply vendor mitigations: Consult F5's official security advisory for CVE-2026-94127 and apply all patches or mitigations F5 has released. F5 is the authoritative source for version-specific guidance.
- Prioritize by BOD 26-04 timelines: Federal agencies are bound by BOD 26-04 patch deadlines. Private organizations are strongly encouraged to follow the same risk-based prioritization.
- Conduct forensic triage: CISA's requirement includes forensic triage. If you cannot immediately patch, review logs for anomalous traffic patterns targeting OAuth endpoints on affected virtual servers and preserve forensic artifacts before applying patches.
- Isolate if no mitigation exists: If no patch or vendor workaround is available for your version, CISA's guidance is to discontinue use of the product or segment it from internet exposure.
- EoTS versions: If any BIG-IP APM instances are running versions that have reached End of Technical Support, treat them as unpatched indefinitely and plan immediate migration or decommission.
How External Security Testing Surfaces This Exposure
Because CVE-2026-94127 is a data plane vulnerability, it exists on the same network paths that carry normal user and application traffic. This makes it well-suited for detection through external, unauthenticated security assessment — the same vantage point an attacker would use.
External testing can help organizations by:
- Identifying internet-exposed BIG-IP APM virtual servers that may be running vulnerable configurations, particularly those presenting OAuth authorization endpoints publicly.
- Fingerprinting service banners and HTTP response characteristics that reveal APM version and OAuth authorization server capabilities without requiring credentials.
- Validating patch status after mitigations are applied, confirming that the remediated version is what is actually running in production — not an untouched standby or overlooked instance.
- Mapping the attack surface across distributed or multi-datacenter deployments where individual teams may not have a consolidated view of all BIG-IP virtual server configurations.
This type of testing does not involve exploitation — it focuses on identifying exposure indicators and confirming remediation, using the same external vantage point a threat actor would assess before attempting to exploit the vulnerability. Organizations uncertain about their BIG-IP APM exposure profile should validate their posture before assuming they are not affected.
Sources & further reading: NVD CVE-2026-94127 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: my.f5.com, cisa.gov. This advisory contains no exploit code.
Frequently asked questions
Does this vulnerability affect BIG-IP systems that only use APM as an OAuth Client or Resource Server?
No. F5 explicitly states that deployments using APM strictly as an OAuth Client or Resource Server — without OAuth Authorization Server profiles configured — are not affected by CVE-2026-94127. Only virtual servers with both an APM access policy and an OAuth Authorization Server profile are vulnerable.
Is the BIG-IP management interface (control plane) exposed by this vulnerability?
No. F5's advisory is explicit: this is a data plane issue with no control plane exposure. The attack surface is the traffic-facing virtual server, not the administrative management interface. That said, RCE on the data plane can still have severe consequences for the system and downstream resources.
Why is CISA's forensic triage requirement significant here?
Because CISA has added this CVE to the KEV catalog — confirming active exploitation — there is a realistic possibility that some affected systems were compromised before a patch was applied. Forensic triage before or alongside patching helps organizations determine whether exploitation occurred, preserve evidence, and understand the scope of any potential incident. Patching alone does not reveal whether a system was already compromised.
What should organizations running End-of-Technical-Support versions do?
F5 does not evaluate EoTS software versions for this vulnerability, meaning no patch will be issued for those versions. Organizations running EoTS versions of BIG-IP APM with the vulnerable configuration should treat those systems as unpatched indefinitely. The appropriate actions are to migrate to a supported version, apply available workarounds, or isolate and discontinue use of the affected instances per CISA's BOD 26-04 guidance.