F5 says specially formed, undisclosed requests can terminate the Traffic Management Microkernel when a virtual server uses an iRule that processes client traffic with this command. An unauthenticated remote attacker can disrupt traffic during the TMM restart and may be able to execute code.F5 classifies the flaw as a stack-based buffer overflow (CWE-121). The company says exposure is confined to the data plane, with no control-plane exposure. Its advisory assigns Critical scores of 9.8 under CVSS 3.1 and 9.3 under CVSS 4.0.
What it allows
How Can CVE-2026-120722 Disrupt Traffic?
The required configuration is a virtual server with an iRule that processes client traffic through DNS::scrape. F5 says undisclosed requests can terminate TMM, forcing a restart that interrupts traffic. The vendor also says remote code execution may be possible; it does not publish an attack sequence.
F5 describes this as a data-plane issue and explicitly rules out control-plane exposure. Teams should prioritize affected virtual servers that receive untrusted traffic and confirm which iRules use the command. That prioritization is our defensive interpretation of F5’s stated trigger.
What Is Known About Exploitation?
The CISA KEV catalog snapshot released on 18 November 2026 did not list this CVE. That catalog status alone cannot determine whether any specific deployment has been attacked. F5 says it discovered the issue internally and does not describe an exploitation incident in its advisory.
Brandefense Blackhole counted one dark-chat post mentioning CVE-2026-120722 from 21 August through 19 November 2026. The measured unit is posts matching this identifier, and the count is a discussion signal. It does not establish an incident or active exploitation.
Who is affected
Which Products and Builds Need Review?
F5 lists BIG-IP DNS 21.1.0, 17.5.0 through 17.5.1, and 17.1.0 through 17.1.3 as vulnerable when the DNS::scrape iRule condition applies. Its table lists BIGIP-21.1.0.4.0.19.3-ENG3 for 21.1.0. For 17.5, it lists BIGIP-17.5.1.11.0.61.12-ENG3 and BIGIP-17.5.1.10.0.80.35-ENG3. For 17.1, it lists BIGIP-17.1.3.7.0.21.4-ENG3 and BIGIP-17.1.3.6.0.14.20-ENG3.
F5 also lists BIG-IP CNF and BIG-IP Next for Kubernetes 2.4.0 through 2.4.2, 2.3.0 through 2.3.4, and 2.2.0 through 2.2.5. Corresponding engineering hotfixes are CNF-2.4.2-EHF13, CNF-2.3.4-EHF13, CNF-2.2.5-EHF13, and BNK equivalents for the same three branches. The vendor marks all other BIG-IP modules and BIG-IQ Centralized Management as not vulnerable in this advisory.
How Should Teams Patch and Verify?
F5 says to install a fix from the matching product and branch table, or move to a branch with a fix. It lists no mitigation for this issue. Engineering hotfix names and the applicable build require manual comparison with the installed software, so this profile supplies no automated version boundary.
Inventory affected virtual servers, confirm the iRule configuration, and record each installed product, branch, and exact build. After installing the applicable F5 hotfix, verify the running build and check that the intended virtual servers still process traffic. Review TMM restart and service-availability records around any unexplained interruptions; these are our defensive checks, not evidence of exploitation.
Record the patch decision in the patch management process. The F5 BIG-IP iRule advisory overview covers separate November 2026 flaws. A vulnerability intelligence platform can help teams organize affected assets and patch evidence.
Timeline
-
2026-11-18
F5 published its advisory and CNA record for CVE-2026-120722.
-
2026-11-19
Brandefense source-pack research captured F5 version tables and the CISA KEV catalog status.
-
2026-11-20
Brandefense reviewed the source evidence and prepared this profile.
What to do
-
Find the affected iRule configuration
Identify virtual servers that process client traffic with DNS::scrape and record their product and exact running build.
-
Match the F5 product table
Compare each BIG-IP DNS, CNF, or Next for Kubernetes branch with its own vulnerable range and engineering hotfix row.
-
Install the applicable F5 fix
Apply the branch-specific fix F5 lists, or upgrade to a branch with a fix when the current branch has none.
-
Verify the running build and service
After maintenance, confirm the installed hotfix and running build, then test traffic through the affected virtual servers.
-
Review unexpected TMM restarts
Inspect service and TMM restart records around unexplained traffic interruptions without attributing them to this CVE without evidence.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-120722 in Brandefense Atlas
The Atlas record of CVE-2026-120722: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does this CVE require an iRule?
Yes. F5 specifies a virtual server with an iRule that processes client traffic using DNS::scrape as the vulnerable configuration.
Can an attacker reach the BIG-IP control plane through this flaw?
F5 says there is no control-plane exposure. It describes the issue as confined to the data plane.
Is remote code execution certain?
F5 says remote code execution may be possible. It confirms that an unauthenticated remote attacker can cause a denial of service.
Which F5 fix should an operator choose?
Use the engineering hotfix listed for the installed product and branch in F5 advisory K000163945. Verify the actual running build afterward.