F5 BIG-IP APM CVE-2026-94127: Fixed Versions and Mitigations

An exploited heap overflow in BIG-IP APM lets an attacker with no login run code on the BIG-IP when APM acts as an OAuth Authorization Server. It affects BIG-IP APM 17.1, 17.5 and 21.1.

Find your fixed version
By CalMax Systems Security Research · Published November 18, 2026 · Last updated: November 18, 2026

What is CVE-2026-94127, and which version fixes it?

CVE-2026-94127 is a heap-based buffer overflow (CWE-122) in F5 BIG-IP Access Policy Manager (APM), rated Critical: CVSS v3.1 9.8 and CVSS v4.0 9.3. On affected builds, specially crafted traffic lets an unauthenticated attacker run code when the virtual server has an APM access policy and an OAuth profile configured for the OAuth Authorization Server role. F5 lists 21.1.0.3, 17.5.1.10 and 17.1.3.6 as the first fixed point releases. The table below also lists later fixed releases and engineering hotfixes for earlier builds. If you also need to address vulnerabilities from F5’s separate November 18 notification, use F5’s hotfix selection guidance for that notification. Follow the forensic triage steps below where required.

For BIG-IP APM, F5 identifies exposure when APM is configured as an OAuth Authorization Server on an affected build. F5 says the flaw has been exploited. CISA added it to its Known Exploited Vulnerabilities catalog on September 22, 2026, and listed September 25, 2026, as the due date. Federal civilian agencies must assess each asset’s internet exposure. For this CVE, CISA’s three-day mitigation window and forensic triage also apply to affected internal assets in scope.

Affected and Fixed BIG-IP APM Versions

F5 advisory K000162605 was published September 22, 2026 and updated October 15, 2026. F5’s release notes confirm the later fixed builds shown here. Find the row for the release you run now.

Branch Affected release family before the listed fix Fixed release Engineering hotfix
BIG-IP APM 21.x21.1.021.1.0.3 (build 20.0) or 21.1.0.4 (build 3.0)Hotfix-BIGIP-21.1.0.2.0.30.22-ENG.iso
BIG-IP APM 17.x17.5.0 through 17.5.117.5.1.10 (build 35.0) or 17.5.1.11 (build 12.0)Hotfix-BIGIP-17.5.1.9.0.160.12-ENG.iso
17.1.0 through 17.1.317.1.3.6 (build 20.0) or 17.1.3.7 (build 4.0)Hotfix-BIGIP-17.1.3.5.0.41.14-ENG
BIG-IP, all other modulesNoneNot applicableNot vulnerable
BIG-IQ Centralized ManagementK000162605 marks BIG-IQ as not vulnerable. F5's BIG-IQ release notes list a fix for this CVE. Ask F5 Support to confirm whether your build is affected and which update to apply.8.4.2.3 (build 8.0), listed under Fixed in this Release as bug 2524777-9—
BIG-IP Next CNF and BIG-IP Next for KubernetesK000162605 marks both products as not vulnerable. F5 release notes nevertheless list fixes for this CVE. Ask F5 Support to confirm exposure and the appropriate update for your platform and build.F5 lists this CVE under Fixed Issues for CNF 2.2.5 on AON, OpenShift and Robin, and for BIG-IP Next for Kubernetes 2.2.5. The CNF 2.4.1 release notes for AON, OpenShift and Robin also list this CVE as fixed.—
F5OS, F5OS-A, F5OS-CNoneNot applicableNot vulnerable
NGINX, F5 Distributed Cloud, NGINX One Console, F5 AI GatewayNoneNot applicableNot vulnerable
How to read the table. F5’s 17.5.1.11 release notes confirm that this later build includes the fix. Check F5’s release notes for the build you plan to deploy. The engineering hotfixes (EHFs) are on F5 Downloads; F5 says they contain all fixes in BIG-IP Hardened Releases 2 (HR2) and refers to K000163302, which says each EHF installs on top of its base release (21.1.0.2, 17.5.1.9 or 17.1.3.5) and requires uploading the corresponding base image before applying the hotfix. Both images must be in /shared/images. If you already run an engineering hotfix, check that the target base image or hotfix includes the fixes you rely on. Open a case with F5 Support if any are missing or unlisted. F5’s advisory writes the 17.1 hotfix name with a space (“Hotfix-BIGIP 17.1.3.5.0.41.14-ENG”); F5’s CVE record uses a hyphen, as in the table. F5 evaluates only releases that have not reached End of Technical Support. If you run a branch that is not in the table, treat it as unassessed and move to a fixed release. F5’s CVE record starts the 17.1 range at 17.1.0. NVD’s CPE analysis starts it at 17.0.0. If you run 17.0.x with APM configured as an OAuth Authorization Server, check your build with F5 Support and plan to move to a fixed release.

What CVE-2026-94127 Does

The flaw is in the OAuth Authorization Server feature of APM, on the traffic side of the BIG-IP.

F5 describes it this way: “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).” F5 tracks it as bug ID 2524777 and classifies it as CWE-122, heap-based buffer overflow. F5 found it internally.

The impact, in F5’s words: it “allows an unauthenticated attacker to perform RCE.” The CVSS vectors from F5 (v3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) mean network reachable, low complexity, no privileges and no user interaction. CISA’s enrichment of the CVE record marks exploitation as active and the flaw as automatable.

Three details narrow who is exposed:

Is your BIG-IP at risk? A BIG-IP is affected if it runs a vulnerable APM build and has a virtual server configured as an OAuth Authorization Server with an APM access policy and an OAuth profile. Check which networks can reach each affected virtual server, including internal networks, when prioritizing remediation.

How to Check Your Version and Exposure

Use F5’s BIG-IP documentation to check the running software and identify virtual servers configured as OAuth Authorization Servers.

1. Find the running version

F5’s K8759: in the Configuration utility, go to System > Configuration; the version is in the Version box. From the command line, enter tmsh, then:

show /sys version

Compare the running version with the table above. In tmsh, use show /sys version detail to verify applied hotfixes. Boot into the volume containing the fixed release or hotfix, then verify the running version on every BIG-IP that runs APM, including both units of an HA pair.

2. Check whether APM is an OAuth Authorization Server

  • Is APM provisioned? Look under System > Resource Provisioning. If APM is not provisioned, this flaw does not apply.
  • Authorization server profiles: look under Access > Federation > OAuth Authorization Server > OAuth Profile. Use the Configuration utility’s Partition selector to check Common and every other administrative partition with an account that can view them. Check OAuth profiles, access profiles, and virtual servers in each partition. An empty list in one partition does not rule out exposure elsewhere.
  • Where they are used: in F5’s setup, the OAuth profile is selected in an access profile (Access > Profiles / Policies > Access Profiles (Per-Session Policies), Configurations area), and that access profile is assigned to a virtual server (Local Traffic > Virtual Servers). Find every access profile that selects an OAuth profile and every virtual server that uses one of those access profiles. Those are the virtual servers F5’s mitigation iRule would go on.
  • Who can reach them: note whether each of those virtual server addresses is reachable from the internet or only from internal networks.

Mitigations Until You Can Upgrade

Installing a fixed release or the engineering hotfix removes the flaw. The steps below only reduce the risk.

Apply F5’s iRule to the affected virtual server

F5’s only listed mitigation is an iRule applied to the affected BIG-IP APM virtual server. It is not published in the advisory: open a case with F5 Support to get it. CISA’s catalog entry calls the iRule a temporary mitigation that allows time for forensic triage, and says to install the final vendor patch as soon as possible after that.

Use the mitigation iRule supplied by F5 Support.

Narrow who can reach the virtual server

This is general practice, not an F5 workaround. If an OAuth authorization server serves only internal users or a known set of partner systems, limit its virtual server to those source networks on the BIG-IP or on the firewall in front. Anything that can still reach it can still attempt the exploit.

Perform forensic triage before patching when BOD 26-04 requires it

CISA flags this CVE for forensic triage under BOD 26-04. For affected federal civilian assets in scope, apply the F5 iRule as temporary mitigation and follow CISA’s forensic triage guidance. Collect volatile data and preserve relevant logs and core files before patching or rebooting when possible, even if an initial log review shows no suspicious activity. Install the final vendor patch as soon as triage is complete. CISA directs agencies to follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. The checks below can help identify signs of prior compromise.

Check for Signs of Compromise

F5 publishes a pattern to look for, not a list of attacker addresses or files.

The pattern F5 describes

F5 says three indicators seen close together in time are a reason to investigate: multiple OAuth authentication failures, followed by suspicious commands, shortly followed by a TMM SIGABRT. Any one of them alone does not mean compromise; the combination and frequency have been seen to correlate with an attack.

1. OAuth failures in /var/log/apm

F5 rates this a medium-confidence indicator. The message is normal in some situations, so the signal is repetition: 10 or more in one log, especially all from a single IP address, should get a human review. The message F5 quotes:

<DATE> <HOST> err tmm1[30975]: 01990004:3: <PROFILE_NAME>: Request UserInfo from Source ID (null) IP <IP> failed. Error Code (invalid_token) Error Description (The access token is invalid.)

F5 also gives this command for APM OAuth statistics. An unexplained increase in total_failed should be investigated:

tmctl global_oauth_stat -s total_requests,total_userinfo_requests,total_failed

2. Audit log around the same time

If you see the OAuth failures, especially in rapid succession or large volume, note the timestamps and review /var/log/audit around those timestamps for suspicious commands, including commands attributed to legitimate accounts.

3. TMM core files

F5 has observed TMM enter a loop, after which the SOD daemon sends it a SIGABRT. A TMM core file alone is not an indicator, but F5 says core files should be investigated.

If you find something

Check for unauthorized changes to the TMM hook that runs after a crash. watchTowr Labs demonstrated a change to that hook in its lab.

  • If you suspect compromise, prioritize collecting volatile evidence, such as memory, and preserve relevant logs and TMM core files before upgrading or rebooting, when possible. Follow your incident response process and the applicable CISA KEV triage instructions.
  • Contact F5 Support and follow your incident response process. Federal civilian agencies should coordinate with CISA on suspected compromise. Under CISA’s Federal Incident Notification Guidelines, report an incident that potentially compromises a federal information system through the CISA Incident Reporting System within one hour of identification by the agency’s top-level incident response team, security operations center or IT department. Send what is known then and update the report as findings come in.
  • Correlate the source address and timestamps with the audit and TMM findings. If you suspect compromise, follow your incident response process to isolate the affected system.

Timeline

DateEvent
September 22, 2026F5 publishes advisory K000162605 and says the flaw has been exploited. The CVE record is published. CISA adds CVE-2026-94127 to the Known Exploited Vulnerabilities catalog.
September 25, 2026Due date listed in CISA KEV. BOD 26-04 governs the applicable actions and timing for each federal civilian agency asset.
October 15, 2026Latest update to F5 advisory K000162605 as of this alert. It lists fixed releases 21.1.0.3, 17.5.1.10 and 17.1.3.6 and the engineering hotfixes.
October 23, 2026F5 releases BIG-IP 21.1.0.4, 17.5.1.11 and 17.1.3.7. The release notes for all three confirm they include the fix for CVE-2026-94127.

Where ThreatListPro Fits

A known-attacker list can cut down who reaches your edge. It does not fix this flaw.

CVE-2026-94127 is a software flaw, and only F5’s fixed release or hotfix removes it. A block list does not stop the exploit: an attacker using an address that is not on the list can still send the malicious traffic.

What a block list can do is reduce the attack traffic that reaches the services you publish. ThreatListPro covers 5.4M+ IPv4 addresses, including addresses covered by CIDR ranges. The list is built from real attacks on live production Palo Alto GlobalProtect VPN portals in the US and is checked for new attackers every 6 hours. ThreatListPro has no BIG-IP setup guide; it is loaded on the firewall in front of the BIG-IP, as a deny rule for inbound traffic. The setup instructions cover the supported firewalls. The list is IPv4 only.

F5 BIG-IP APM CVE-2026-94127 FAQs

Is CVE-2026-94127 being exploited?

Yes. F5 says this vulnerability has been exploited. F5 published its advisory and CISA added CVE-2026-94127 to KEV on September 22, 2026. The catalog lists September 25, 2026, as the due date. CISA’s three-day mitigation window and forensic triage also apply to affected internal assets in scope for federal civilian agencies.

Which BIG-IP version fixes CVE-2026-94127?

F5 lists BIG-IP 21.1.0.3, 17.5.1.10 and 17.1.3.6 as the first fixed point releases. It also lists three engineering hotfixes: Hotfix-BIGIP-21.1.0.2.0.30.22-ENG, Hotfix-BIGIP-17.5.1.9.0.160.12-ENG and Hotfix-BIGIP-17.1.3.5.0.41.14-ENG. The later releases in the table also include the fix. F5 identifies affected builds in the 21.1.0, 17.5.0 through 17.5.1, and 17.1.0 through 17.1.3 release families when APM is configured as an OAuth Authorization Server.

Am I affected if BIG-IP APM is only an OAuth client?

No, according to F5. The flaw is only present when BIG-IP APM is configured as an OAuth Authorization Server, with an access policy and an OAuth profile on a virtual server. F5 says deployments that use APM strictly as an OAuth Client or Resource Server, without OAuth authorization server profiles, are not affected.

Does an attacker need a password to exploit CVE-2026-94127?

No. F5 says the flaw allows an unauthenticated attacker to perform remote code execution. The CVSS v3.1 score is 9.8 and the CVSS v4.0 score is 9.3, both Critical, with no privileges or user interaction required.

Is there a workaround for CVE-2026-94127?

Open a case with F5 Support to request the iRule and apply it to the affected BIG-IP APM virtual server. For assets subject to CISA’s forensic triage requirement, use the iRule as a temporary mitigation, complete triage, and install the final vendor patch as soon as possible.

Is the BIG-IP management interface affected by CVE-2026-94127?

F5 calls this a data plane issue with no control plane exposure. The risk is the virtual server that carries the APM access policy and the OAuth profile, not the management port. F5 also says BIG-IP systems in Appliance mode are vulnerable.

What are the indicators of compromise for CVE-2026-94127?

F5 lists no IP addresses or file hashes. Investigate repeated OAuth failures in /var/log/apm followed by suspicious commands in /var/log/audit and then a TMM SIGABRT shortly afterward. On its own, 10 or more of those OAuth failures in one log already warrants a human review, and F5 says any TMM core file should be investigated.

Sources

Block Known Attackers at the Firewall in Front

ThreatListPro covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours. Monthly is $19.99 with a 14-day free trial and no card needed.

Start a 14-day free trial Or test the free sample first: no signup

Firewall Guides

ThreatListPro uses a plain-text feed for firewalls that support external IPv4 address lists.

Palo Alto FortiGate pfSense OPNsense SonicWall Cisco ASA Sophos XG UniFi

Related Resources

More dated alerts, and how to block addresses at the firewall in front of an exposed service.

All Security Alerts Ivanti Connect Secure CVE-2026-104935 Check Point CVE-2026-123039 Setup Instructions for Every Supported Firewall Block an IP Address at the Firewall IP Blocklist vs Threat Feed