Skip to main content
Mallory
CriticalVulnerability

CVE-2026-120722: Stack-based buffer overflow in F5 BIG-IP iRule DNS::scrape

Published Nov 18, 2026 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days22 mentions · peak 11 in a dayToday
CVSS9.3Critical · v4
EPSS0.77%56th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-120722CWE-121 · Stack-based Buffer Overflow

CVE-2026-120722 is a stack-based buffer overflow affecting F5 BIG-IP DNS and BIG-IP Next for Kubernetes when a virtual server is configured with an iRule that processes client traffic using DNS::scrape. Undisclosed requests can terminate the Traffic Management Microkernel (TMM), disrupting traffic while it restarts, and may enable remote code execution. Exploitation is remote and unauthenticated. The vulnerability affects only the data plane; there is no control plane exposure. F5 rates it Critical, with CVSS v3.1 and v4.0 scores of 9.8 and 9.3, respectively.

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.

A remote, unauthenticated attacker can terminate TMM and cause denial of service on the affected BIG-IP system. Traffic handled by TMM is disrupted during restart, potentially interrupting applications and services even when their backend systems remain operational. Successful exploitation may also permit remote code execution on the affected device, although code execution is not established as a guaranteed outcome. The vulnerability does not directly expose the management control plane.

Mitigation

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

F5 lists no mitigation or workaround for this vulnerability. Restricting access to the management interface does not address exposure through an affected traffic-handling virtual server.

Remediation

Patch, then assume compromise.

Install the F5 engineering hotfix matching the exact product and installed build. For BIG-IP DNS, the listed fixes are BIGIP-17.1.3.7.0.21.4-ENG for affected 17.1.x base releases, BIGIP-17.5.1.11.0.61.12-ENG for affected 17.5.x base releases, and BIGIP-21.1.0.4.0.19.3-ENG for 21.1.0. Systems running BIGIP-17.1.3.6.0.9.20-ENG require BIGIP-17.1.3.6.0.14.20-ENG. Systems running BIGIP-17.5.1.10.0.7.35-ENG or BIG-IP-17.5.1.10.0.37.35-ENG require BIGIP-17.5.1.10.0.80.35-ENG. For BIG-IP Next for Kubernetes, install BNK-2.2.5-EHF1, BNK-2.3.4-EHF1, or BNK-2.4.2-EHF1 for the corresponding release branch. Consult F5 advisories K000163945 and K000164239 before selecting a package; contact F5 Support for replacement custom builds. If the installed branch has no fix, upgrade to a version containing the fix. Engineering hotfixes receive less extensive QA testing than scheduled releases. Validate live traffic after installation. Confirm BIG-IP CNF applicability directly with F5 because its product advisory and updated CVE record disagree on whether CNF is affected.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-120722 exploited in the wild?
As of Nov 21, 2026, Mallory has no reports of CVE-2026-120722 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-120722?
As of Nov 21, 2026, Mallory has found no public exploit for CVE-2026-120722.
Is there a patch for CVE-2026-120722?
Install the F5 engineering hotfix matching the exact product and installed build. For BIG-IP DNS, the listed fixes are BIGIP-17.1.3.7.0.21.4-ENG for affected 17.1.x base releases, BIGIP-17.5.1.11.0.61.12-ENG for affected 17.5.x base releases, and BIGIP-21.1.0.4.0.19.3-ENG for 21.1.0.
How severe is CVE-2026-120722?
CVE-2026-120722 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 0.77% (56th percentile) as of Nov 21, 2026.
Activity feed

Recent activity

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

View more in app →
cryptika blogNews · Nov 21, 20266 Critical F5 BIG-IP Vulnerabilities Could Let Hackers Disrupt Websites and Execute Malicious Code | Cryptika CybersecurityA critical memory-corruption vulnerability affecting BIG-IP iRules configurations. The six critical flaws can allow unauthenticated remote attackers to crash the Traffic Management Microkernel, disrupting websites and other services, and potentially execute code. F5 released emergency hotfixes and reported no exploitation at disclosure.Read more ↗cyber security newsNews · Nov 21, 20266 Critical F5 BIG-IP Vulnerabilities Could Let Hackers Disrupt Websites and Execute Malicious CodeA critical BIG-IP memory-corruption vulnerability affecting iRules configurations. The article describes the six critical issues collectively as enabling unauthenticated denial of service through Traffic Management Microkernel crashes and potentially code execution.Read more ↗csirt skNews · Nov 20, 2026F5 opravila šesť kritických zraniteľností v BIG-IP | CSIRT.SKCritical stack-based buffer overflow affecting BIG-IP traffic processing when a virtual server has an iRule using DNS::scrape. An unauthenticated remote attacker can terminate or restart TMM, causing denial of service, and potentially execute code. The data plane is affected, not the management interface. CVSS v4: 9.3. F5 engineering hotfixes are available.Read more ↗gm csirtNews · Nov 20, 2026Multiple Vulnerabilities in F5 Products (BIG-IP, BIG-IQ, NGINX, and NGINX Plus) - gmcsirtCritical vulnerability affecting BIG-IP iRules. The advisory does not specify its individual exploitation mechanism or impact.Read more ↗
+9 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 signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.