F5 Patches Exploited BIG-IP APM Zero-Day in OAuth Servers
By @sharedot · · 8 pages
- Cybersecurity
- F5 Big Ip
- Zero Day
- Cve 2026 94127
F5 shipped hotfixes for CVE-2026-94127, a 9.8-rated BIG-IP APM zero-day letting attackers run code unauthenticated on OAuth authorization servers.
What Happened
F5 disclosed on September 22 that attackers are exploiting a critical flaw, CVE-2026-94127, in BIG-IP Access Policy Manager that lets an unauthenticated attacker run arbitrary code on a vulnerable BIG-IP system.
The company confirmed the vulnerability has been exploited in the wild and released engineering hotfixes for all three affected branches.
The flaw is a heap-based buffer overflow rated 9.8 on CVSS v3.1 and 9.3 on CVSS v4.0, and it exists only where APM serves as an OAuth authorization server issuing access tokens to applications.
Why It's Surprising
Restricting access to the BIG-IP management interface offers no protection at all, because the malicious traffic targets the data plane virtual server that receives OAuth traffic rather than the control plane.
BIG-IP systems running in Appliance mode are also vulnerable, and F5 says only APM deployments acting as OAuth clients or resource servers escape exposure.
The affected setup — an APM access policy and an OAuth authorization server profile on the same virtual server — is a configuration edge administrators could easily overlook while assuming their appliances were safe behind a locked-down management plane.
The Evidence
CISA added the flaw to its Known Exploited Vulnerabilities catalog on September 22, the same day F5 disclosed it, and gave federal civilian agencies until September 25 to apply mitigations.
Security Affairs reports that Shadowserver is tracking more than 14,700 IP addresses showing BIG-IP APM fingerprints, though that number does not indicate how many systems are actually vulnerable. CERT-EU, the cybersecurity service for EU institutions, also published an advisory.
F5 updated its CVE record at 00:45 UTC on September 23 to narrow the condition to the authorization server role, after CISA and CERT-EU had described it more broadly.
The Stakes
BIG-IP appliances typically sit at the edge of corporate networks handling authentication and access to internal applications, so a successful compromise hands attackers a privileged foothold for moving deeper into an organization's infrastructure.
Neither F5's CVE record nor the CISA and CERT-EU advisories say how many systems were attacked, who the attackers are, or which organizations were targeted, and it remains unclear whether installing the hotfix removes access an attacker already gained.
End-of-support BIG-IP versions were not evaluated by F5, so their status is unknown rather than safe.
Affected Versions and Fixes
Systems running BIG-IP 21.1.0 need Hotfix-BIGIP-21.1.0.2.0.30.22-ENG, versions 17.5.0 through 17.5.1 need Hotfix-BIGIP-17.5.1.9.0.160.12-ENG, and 17.1.0 through 17.1.3 need Hotfix-BIGIP-17.1.3.5.0.41.14-ENG.
Running the latest 17.x point release is not enough — only the engineering hotfix closes the flaw, and a system updated to a build inside the affected ranges still needs the hotfix if APM acts as an OAuth authorization server.
Organizations that cannot patch immediately can request an iRule mitigation for the affected virtual server by opening a ticket with F5 support, a temporary measure rather than a patch replacement.
Checking for Compromise
The combination that should trigger human review is repeated OAuth authentication failures, then suspicious commands, then a TMM SIGABRT shortly afterward.
Administrators should look for ten or more failed UserInfo requests with the error 'The access token is invalid' in /var/log/apm, ideally from a single IP within a short window, plus an unexplained rise in total_failed from the tmctl global_oauth_stat command, suspicious entries in /var/log/audit, and any TMM core files.
CISA told agencies to apply the iRule first to allow proactive forensic triage and then install the final patch as soon as possible; CERT-EU advises preserving forensic evidence, applying the hotfix, checking for compromise, and starting incident response if any signs are found.