Skip to content
NewA calmer, faster ZeroHour

F5 patches six critical BIG-IP flaws that can crash traffic or run code

Original title: 6 Critical F5 BIG-IP Vulnerabilities Could Let Hackers Disrupt Websites and Execute Malicious Code

Cyber Security Newsby Guru Baran ()3 min read2
Part of a story covered by 5 sourcesF5 ships hotfixes for critical BIG-IP APM and iRules flawsMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

F5 said no exploitation was known on November 18; engineering hotfixes cover TMOS 17.1.x, 17.5.x and 21.1.x, with no workaround.

F5 issued an out-of-band notification on November 18 for six critical BIG-IP data-plane flaws. A remote attacker who can reach an affected service may crash the Traffic Management Microkernel and take websites or other services offline, and F5 warned code execution may also be possible. Five flaws involve iRules; CVE-2026-123637 affects Access Policy Manager. F5 listed no workaround and said exploitation had not been reported.

Unconfirmed: F5 said no exploitation had been reported at disclosure; later exploitation is not addressed.

Key facts
  • Vulnerable BIG-IP ranges include 17.1.0–17.1.3, 17.5.0–17.5.1 and 21.1.0.
  • Next for Kubernetes and CNF lines 2.2 through 2.4 have EHF1 fixes.
  • A separate high-severity SSO flaw, CVE-2026-126822, is outside the six.
  • Keeping the management interface offline does not protect a reachable affected service.
Security assessment · AI, from the articleNo known exploitation

Impact: Unauthenticated service outage or possible code execution

ProductAffectedFixed in
F5 BIG-IP17.1.0–17.1.3; 17.5.0–17.5.1; 21.1.0BIGIP-17.1.3.7.0.21.4-ENG; BIGIP-17.5.1.11.0.61.12-ENG; BIGIP-21.1.0.4.0.19.3-ENG
F5 BIG-IP Next for Kubernetes2.2.0–2.2.5; 2.3.0–2.3.4; 2.4.0–2.4.2BNK-2.2.5-EHF1; BNK-2.3.4-EHF1; BNK-2.4.2-EHF1
F5 BIG-IP Cloud-Native Network Functions2.2.0–2.2.5; 2.3.0–2.3.4; 2.4.0–2.4.2CNF-2.2.5-EHF1; CNF-2.3.4-EHF1; CNF-2.4.2-EHF1
What to do
  1. 1.Install the engineering hotfix that matches the exact installed TMOS or Next build.
  2. 2.Prioritize internet-facing virtual servers and traffic for critical services.
  3. 3.Contact F5 Support if the device runs a custom build.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2026-116953
+5 related CVEs
DoS and possible RCE in F5 BIG-IP via GENERICMESSAGE::route iRule
9.3—

From the original article

3 min read at cybersecuritynews.com

F5 released emergency fixes for six critical BIG-IP vulnerabilities that could let remote attackers take websites and other services offline without logging in. The flaws affect specific traffic-handling configurations. An attacker who can reach a vulnerable service could crash the BIG-IP process that handles client traffic.

Cyber Security News

By Guru Baran · cybersecuritynews.com

Read the full article at Cyber Security News

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.