SAASMENT

News

Six critical BIG-IP flaws can crash traffic before anyone logs in.

F5 says six critical data-plane bugs can crash BIG-IP traffic without a login, and may allow remote code execution, when a virtual server uses a specific iRule or APM policy. The fixes are engineering hotfixes, and F5 lists no workaround.

Illustration of traffic lanes shattering against a cracked gateway

Impact

What was impacted
Six stack-based buffer overflows in the BIG-IP data plane (the Traffic Management Microkernel), each scored 9.8 on CVSS 3.1 and 9.3 on CVSS 4.0. F5 says the management plane is not exposed. A crash stops traffic until TMM restarts, and F5 says remote code execution may also be possible. Each flaw needs one virtual-server setup: CVE-2026-123637, an APM per-request policy with both the Client Information agent and Endpoint Security agents (BIG-IP APM only); CVE-2026-121805, an iRule using PEM::subscriber on client traffic (BIG-IP PEM, BIG-IP Next for Kubernetes, and as of 18 November 2026 BIG-IP CNF); CVE-2026-120292, an HTTP profile and an iRule using MR::message route (BIG-IP all modules, and BIG-IP Next for Kubernetes); CVE-2026-120285, an HTTP profile and an iRule using PSC::ip_address (BIG-IP all modules, BIG-IP Next for Kubernetes, and as of that day BIG-IP CNF); CVE-2026-116953, an iRule using GENERICMESSAGE::route on client traffic (BIG-IP all modules, and BIG-IP Next for Kubernetes); CVE-2026-120722, an iRule using DNS::scrape on client traffic (BIG-IP DNS and BIG-IP Next for Kubernetes). F5’s advisory lists BIG-IP CNF as not vulnerable to CVE-2026-120722, while the CVE record updated the same day lists CNF as affected.
Who was impacted
Operators of supported BIG-IP systems that use those iRules or APM agents, plus BIG-IP Next for Kubernetes 2.2.0–2.2.5, 2.3.0–2.3.4, and 2.4.0–2.4.2, and BIG-IP CNF on the same ranges for CVE-2026-121805 and CVE-2026-120285. F5 only evaluated versions still in technical support, so an older release missing from the tables has not been shown to be safe. WatchTowr researcher Sina Kheirkhah reported four of the six; F5 found the other two. None of the advisories says they have been exploited. They are separate from CVE-2026-94127, the APM OAuth heap overflow disclosed on 22 September 2026 and added to CISA’s Known Exploited Vulnerabilities catalog that day.
What you need to do
Install the engineering hotfix for your supported branch. No scheduled release is listed as a fix for these six, and the advisories give no workaround until the hotfix is installed. F5 says engineering hotfixes skip the full quality assessment of a scheduled release and come with no warranty. A system already on a custom engineering hotfix needs a new build from F5 support. BIG-IP Next for Kubernetes 2.4.0–2.4.2, 2.3.0–2.3.4, and 2.2.0–2.2.5 is fixed in BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, and BNK-2.2.5-EHF1. BIG-IP CNF on those same ranges is fixed in CNF-2.4.2-EHF1, CNF-2.3.4-EHF1, and CNF-2.2.5-EHF1 for CVE-2026-121805 and CVE-2026-120285. Also patch the six lower-rated BIG-IP and BIG-IQ flaws disclosed the same day, listed in the brief, where those features are in use.

F5 disclosed six critical vulnerabilities in BIG-IP that let an attacker crash the Traffic Management Microkernel without logging in. Traffic stays disrupted until TMM restarts. Each flaw is a stack-based buffer overflow in the data plane, the part that processes almost all network traffic. F5 says the management side is not exposed, and that the flaws may also allow remote code execution. All six are scored 9.8 on CVSS 3.1 and 9.3 on CVSS 4.0. Each one needs a specific setup on a virtual server: an iRule that uses a particular command, or an APM policy that includes two particular kinds of agent. None of the advisories says the flaws have been exploited. WatchTowr researcher Sina Kheirkhah reported four of them. F5 found the other two. Today’s six are separate from CVE-2026-94127, the APM heap overflow F5 disclosed on 22 September 2026. CISA added that earlier bug to the Known Exploited Vulnerabilities catalog the same day. It hits APM when it is an OAuth authorization server and lets attackers run code without logging in. Today’s six need different settings.

CVE-2026-123637 needs an APM per-request policy that includes both the Client Information agent and Endpoint Security agents, and it affects BIG-IP APM only. CVE-2026-121805 needs an iRule that uses PEM::subscriber on client traffic. It affects BIG-IP PEM, BIG-IP Next for Kubernetes, and, as of 18 November 2026, BIG-IP CNF. CVE-2026-120292 needs an HTTP profile and an iRule that uses MR::message route. It affects BIG-IP (all modules) and BIG-IP Next for Kubernetes. CVE-2026-120285 needs an HTTP profile and an iRule that uses PSC::ip_address. It affects BIG-IP (all modules), BIG-IP Next for Kubernetes, and, as of that day, BIG-IP CNF. CVE-2026-116953 needs an iRule that uses GENERICMESSAGE::route on client traffic. It affects BIG-IP (all modules) and BIG-IP Next for Kubernetes. CVE-2026-120722 needs an iRule that uses DNS::scrape on client traffic. It affects BIG-IP DNS and BIG-IP Next for Kubernetes. F5’s advisory lists BIG-IP CNF as not vulnerable to that last flaw, but the CVE record, updated the same day, lists CNF as affected.

For the six critical flaws, the only fixes are engineering hotfixes, builds F5 issues between normal software releases. No scheduled release is listed as a fix, and the advisories provide no workaround until a hotfix is installed. F5 warns that engineering hotfixes do not get the full quality assessment of a scheduled release, and its hotfix policy says they come with no warranty. A system already running a custom engineering hotfix needs a new one from F5 support. BIG-IP Next for Kubernetes 2.4.0 to 2.4.2, 2.3.0 to 2.3.4, and 2.2.0 to 2.2.5 is fixed in BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, and BNK-2.2.5-EHF1. BIG-IP CNF, on the same version ranges, is fixed in CNF-2.4.2-EHF1, CNF-2.3.4-EHF1, and CNF-2.2.5-EHF1 for CVE-2026-121805 and CVE-2026-120285. F5 checks only versions still in technical support, so an older release that is missing from the tables has not been shown to be safe. The same day’s security notification lists 22 advisories, including 10 for NGINX.

The same advisories cover six lower-rated flaws in BIG-IP and BIG-IQ. Scores below are CVSS 3.1. CVE-2026-125274 (iControl SOAP, 8.8) lets a user with network access and at least the Guest role send an unauthorized management request. F5 says this may allow system commands, creating or deleting files, or disabling services. It is fixed in BIG-IP 21.1.0.3, 17.5.1.10, and 17.1.3.6, and in BIG-IQ 8.4.2.3. Until then, limit iControl SOAP to trusted networks. Blocking it on self-IP addresses may break high-availability setups. CVE-2026-120718 (iControl REST, 8.1) covers tokens that may not expire as expected. Someone who already holds a token may keep it valid until the owner deletes it. It is fixed in BIG-IP 21.1.0.2, 17.5.1.10, and 17.1.3.6. Scripts that create tokens can delete them when they are no longer needed. CVE-2026-125272 (APM, 7.5) crashes TMM without a login when a per-request policy has a form-based Logon Page, and it is fixed in the same engineering hotfixes as the six critical flaws. CVE-2026-126822 (APM SAML, 7.5) crashes TMM without a login when an access profile is a SAML service provider, and uses the same hotfixes. Until then, F5 suggests removing the SAML Auth agent if SAML SP is not needed, and limiting that virtual server to trusted clients. CVE-2026-126336 (APM SAML, 7.5) crashes TMM without a login when a SAML SP agent has encrypted assertions turned on. It is fixed in BIG-IP 21.1.0.3, 17.5.1.10, and 17.1.3.6. F5 recommends a high-availability setup to reduce the impact. CVE-2026-121812 (APM and SSL Orchestrator, 7.5) crashes TMM when a per-request policy has the tmm.access.policytrace database key turned on. The key is off by default. APM is fixed in the same engineering hotfixes. For SSL Orchestrator, the advisory lists fixes on the 21.1 and 17.1 branches only.

For your AI agent

Agent instructions — copy paste to Claude

You are helping me respond to six critical BIG-IP data-plane flaws disclosed by F5 on 18 November 2026. Each is a stack-based buffer overflow in the Traffic Management Microkernel, scored 9.8 (CVSS 3.1) and 9.3 (CVSS 4.0). An attacker who is not logged in can crash TMM, which disrupts traffic until TMM restarts, and F5 says remote code execution may also be possible. The management plane is not exposed. Each flaw needs a specific virtual-server setup. None of the advisories says these six have been exploited. WatchTowr researcher Sina Kheirkhah reported four; F5 found two. They are separate from CVE-2026-94127, the September 22 2026 APM OAuth heap overflow that CISA listed as exploited.

The six critical flaws and the setup each one needs:
- CVE-2026-123637: APM per-request policy with both the Client Information agent and Endpoint Security agents. BIG-IP APM only.
- CVE-2026-121805: iRule using PEM::subscriber on client traffic. BIG-IP PEM, BIG-IP Next for Kubernetes, and as of 18 November 2026 BIG-IP CNF.
- CVE-2026-120292: HTTP profile and an iRule using MR::message route. BIG-IP (all modules) and BIG-IP Next for Kubernetes.
- CVE-2026-120285: HTTP profile and an iRule using PSC::ip_address. BIG-IP (all modules), BIG-IP Next for Kubernetes, and as of that day BIG-IP CNF.
- CVE-2026-116953: iRule using GENERICMESSAGE::route on client traffic. BIG-IP (all modules) and BIG-IP Next for Kubernetes.
- CVE-2026-120722: iRule using DNS::scrape on client traffic. BIG-IP DNS and BIG-IP Next for Kubernetes. F5’s advisory lists BIG-IP CNF as not vulnerable; the CVE record updated the same day lists CNF as affected.

Fixes for the six are engineering hotfixes only. No scheduled release is listed, and F5 lists no workaround until the hotfix is installed. F5 says these hotfixes skip full release QA and come with no warranty. A box already on a custom engineering hotfix needs a new one from F5 support. BIG-IP Next for Kubernetes 2.4.0–2.4.2, 2.3.0–2.3.4, and 2.2.0–2.2.5: BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, BNK-2.2.5-EHF1. BIG-IP CNF on the same ranges, for CVE-2026-121805 and CVE-2026-120285: CNF-2.4.2-EHF1, CNF-2.3.4-EHF1, CNF-2.2.5-EHF1. Versions outside technical support were not evaluated, so a missing row is not proof of safety.

Same-day lower-rated flaws (CVSS 3.1):
- CVE-2026-125274, iControl SOAP, 8.8. Guest or higher, network access, unauthorized management request that F5 says may allow system commands, file create/delete, or disabling services. Fixed in BIG-IP 21.1.0.3, 17.5.1.10, 17.1.3.6 and BIG-IQ 8.4.2.3. Until then, limit iControl SOAP to trusted networks. Blocking it on self-IP addresses may break high availability.
- CVE-2026-120718, iControl REST, 8.1. Tokens may not expire; a holder can keep one valid until the owner deletes it. Fixed in BIG-IP 21.1.0.2, 17.5.1.10, 17.1.3.6. Scripts can delete tokens when finished.
- CVE-2026-125272, APM, 7.5. Form-based Logon Page in a per-request policy can crash TMM with no login. Same engineering hotfixes as the six critical flaws.
- CVE-2026-126822, APM SAML, 7.5. SAML service-provider access profile can crash TMM with no login. Same hotfixes. Until then, remove the SAML Auth agent if SAML SP is unused, and limit that virtual server to trusted clients.
- CVE-2026-126336, APM SAML, 7.5. Encrypted assertions on a SAML SP agent can crash TMM with no login. Fixed in BIG-IP 21.1.0.3, 17.5.1.10, 17.1.3.6. F5 recommends high availability to reduce impact.
- CVE-2026-121812, APM and SSL Orchestrator, 7.5. tmm.access.policytrace turned on (off by default) can crash TMM. APM uses the same critical hotfixes. SSL Orchestrator fixes are listed on the 21.1 and 17.1 branches only.

Context:
- What was impacted: BIG-IP TMM on virtual servers with the iRules or APM agents above, plus the management interfaces for the iControl bugs.
- Who should care: BIG-IP, BIG-IP Next for Kubernetes, BIG-IP CNF, and BIG-IQ operators on supported releases that use those features.
- What to do: install the matching engineering hotfix or fixed build. Do not invent a workaround for the six critical flaws.

Do this in order. Ask before installing a hotfix, changing a virtual server, editing iRules, or restricting iControl. Prefer read-only inventory first. Do not write or run an exploit or a crash proof of concept.

1. Inventory
   - Record BIG-IP, BIG-IQ, BIG-IP Next for Kubernetes, and BIG-IP CNF versions, including any custom engineering hotfix already installed.
   - Search iRules for PEM::subscriber, MR::message route, PSC::ip_address, GENERICMESSAGE::route, and DNS::scrape on client traffic, and note HTTP profiles on those virtual servers.
   - Find APM per-request policies that combine the Client Information agent and Endpoint Security agents, form-based Logon Pages, SAML SP (including encrypted assertions), and whether tmm.access.policytrace is on.
   - Note whether iControl SOAP and iControl REST are reachable beyond trusted networks.
2. Contain
   - F5 lists no workaround for the six critical flaws. Do not disable production iRules on your own. Propose network limits only where F5 published them: iControl SOAP to trusted networks (avoid breaking HA on self-IPs), unused SAML Auth agent removal, and trusted-client limits for a SAML SP virtual server. Ask before applying them.
   - For CVE-2026-120718, propose deleting REST tokens when scripts are done, until the fixed build is in.
3. Remediate
   - Plan the engineering hotfix for the branch in support. For Next for Kubernetes and CNF, use the BNK and CNF EHF builds named above. A custom hotfix needs a replacement from F5 support. Ask before the install, because these builds skip full release QA.
   - Plan the fixed BIG-IP and BIG-IQ versions for CVE-2026-125274, CVE-2026-120718, and CVE-2026-126336.
4. Verify
   - After install, record the running version or hotfix ID and confirm TMM came back. Note any virtual server still matching a vulnerable iRule or APM setup on an unfixed build.
5. Report back
   - Versions found, which of the twelve flaws match this environment, hotfixes applied, workarounds still in place, and anything F5 did not evaluate because it is out of support.

Do not invent hotfix IDs, module names, or exploit conditions. If a check needs access I have not given you, say what you need and stop.

← All news

Try the platform.

Open the demo workspace with mock data. No login. Register from the banner when you want early access. No security team. No call.

Try the platform