Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-94127: Unauthenticated OAuth RCE in F5 BIG-IP APM

Published Sep 22, 2026 · Updated 2 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 2 in a dayToday
CVSS9.3Critical · v4
EPSS26.6%98th percentile
CISA KEVYesAdded Sep 22, 2026
In the wildActivePer CISA KEV
Vendor
F5
IdentifiersCVE-2026-94127CWE-122 · Heap-based Buffer Overflow

CVE-2026-94127 is a heap-based buffer overflow in F5 BIG-IP Access Policy Manager (APM) OAuth processing. When APM operates as an OAuth Authorization Server and a virtual server has both an APM access policy and an OAuth profile, an unauthenticated attacker can trigger the vulnerability through specially crafted network traffic. OAuth request processing copies an oversized HTTP Authorization header into a fixed-size 0x4100-byte heap buffer without adequate bounds checking, allowing memory corruption and potentially arbitrary code execution in the Traffic Management Microkernel (TMM). Affected releases include unpatched BIG-IP APM 21.1.0, 17.5.0–17.5.1, and 17.1.0–17.1.3. Appliance mode is also affected. Deployments operating exclusively as OAuth Clients or Resource Servers without authorization-server profiles are not affected. Exploitation occurs through the data plane, with no direct control-plane exposure. F5 confirmed exploitation in the wild.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits unauthenticated remote arbitrary code execution on an affected BIG-IP appliance, threatening confidentiality, integrity, and availability. Exploitation can also crash TMM and disrupt traffic processing. Compromise may expose or permit manipulation of access policies, session material, credentials, and OAuth tokens, potentially endangering downstream services that trust the appliance. The vulnerability does not directly expose the management control plane.

Mitigation

If you can’t patch tonight, do this now.

If patching must be delayed, obtain the vendor-provided mitigation iRule from F5 Support and apply it to every affected virtual server. Restrict access to affected OAuth services to trusted client networks where operationally possible. Restricting only the management interface does not prevent exploitation. Investigate correlated bursts of OAuth UserInfo invalid-token failures, unexplained increases in OAuth failure counters, suspicious audit-log commands, and TMM crashes or SIGABRT events. Individual indicators alone do not establish compromise.

Remediation

Patch, then assume compromise.

Immediately install the applicable F5 engineering hotfix: Hotfix-BIGIP-21.1.0.2.0.30.22-ENG for 21.1.0; Hotfix-BIGIP-17.5.1.9.0.160.12-ENG for 17.5.0–17.5.1; or Hotfix-BIGIP-17.1.3.5.0.41.14-ENG for 17.1.0–17.1.3. Consult F5 advisory K000162605 for the latest hotfix revision, including Update 1 for the 17.1 correction, installation prerequisites, and fixed-release applicability. Older affected releases may require an intermediate upgrade before hotfix installation. Migrate unsupported releases to a supported fixed release; end-of-support versions were not evaluated. Preserve forensic evidence where feasible and investigate prior compromise. Patching closes the vulnerability but does not remove attacker access already established.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
F5Big-Ip Access Policy Managerapplication
FAQ

Frequently asked questions

Is CVE-2026-94127 exploited in the wild?
Yes. As of Nov 20, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Sep 22, 2026.
Is there a public exploit for CVE-2026-94127?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-94127, the earliest disclosed Sep 24, 2026.
Is there a patch for CVE-2026-94127?
Immediately install the applicable F5 engineering hotfix: Hotfix-BIGIP-21.1.0.2.0.30.22-ENG for 21.1.0; Hotfix-BIGIP-17.5.1.9.0.160.12-ENG for 17.5.0–17.5.1; or Hotfix-BIGIP-17.1.3.5.0.41.14-ENG for 17.1.0–17.1.3. Consult F5 advisory K000162605 for the latest hotfix revision, including Update 1 for the 17.1 correction, installation prerequisites, and fixed-release applicability.
What products are affected by CVE-2026-94127?
F5 Big-Ip Access Policy Manager.
How severe is CVE-2026-94127?
CVE-2026-94127 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 26.6% (98th percentile) as of Nov 20, 2026.
Activity feed

Recent activity

259 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+22 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity171Community discussion across Reddit, Mastodon, and other social sources.