F5 discloses six critical BIG-IP flaws that can crash traffic
Original title: F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE
Each flaw needs a specific iRule or APM setup; F5 offers only engineering hotfixes and lists no workaround.
F5 disclosed six critical stack-based buffer overflows in BIG-IP that can let an unauthenticated attacker crash the Traffic Management Microkernel and disrupt traffic until it restarts. The company says the flaws may also allow remote code execution, but only when a virtual server uses a particular iRule command or APM agents. All six score 9.8 on CVSS v3.1, and none of the advisories says they have been exploited. Fixes are engineering hotfixes rather than scheduled releases. Six additional lower-rated BIG-IP and BIG-IQ flaws were disclosed the same day.
Unconfirmed: The company advisory and an updated CVE record disagree on whether BIG-IP CNF is affected.
- WatchTowr's Sina Kheirkhah reported four of the critical flaws; F5 found two.
- BIG-IP Next for Kubernetes fixes include BNK-2.4.2-EHF1, BNK-2.3.4-EHF1 and BNK-2.2.5-EHF1.
- F5 warns engineering hotfixes lack the QA of scheduled releases.
- CVE-2026-125274 in iControl SOAP scores 8.8 and is fixed in named BIG-IP and BIG-IQ builds.
- Today's flaws differ from previously exploited CVE-2026-94127.
Impact: Unauthenticated TMM crash and possible remote code execution
| Product | Affected | Fixed in |
|---|---|---|
| F5 BIG-IP | — | engineering hotfixes |
| F5 BIG-IP Next for Kubernetes | 2.4.0 to 2.4.2, 2.3.0 to 2.3.4, 2.2.0 to 2.2.5 | BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, BNK-2.2.5-EHF1 |
- 1.Install the engineering hotfix that matches the affected BIG-IP product and version.
- 2.For CVE-2026-125274, limit iControl SOAP access to trusted networks until patched.
Vulnerabilities mentioned
All| CVE | Vulnerability | CVSS | EPSS | Signals | Published |
|---|---|---|---|---|---|
| CVE-2026-116953 | DoS and possible RCE in F5 BIG-IP via GENERICMESSAGE::route iRule | 9.3 group max | — | ||
| CVE-2026-125274 | Management request injection in F5 iControl SOAP (Guest+) | 8.7 | — |
Indicators of compromise
auto-extracted · verify before use · export allAll| Type | Indicator | Context |
|---|---|---|
| ipv4 | 17.1.3.6 | ble 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, the SOAP advisory expla |
| ipv4 | 17.5.1.10 | files, or disable 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, the SOAP a |
| ipv4 | 21.1.0.2 | ys valid unless its owner deletes it. It is fixed in BIG-IP 21.1.0.2, 17.5.1.10, and 17.1.3.6. As a workaround, scripts that cre |
| ipv4 | 21.1.0.3 | or delete files, or disable 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, |
| ipv4 | 8.4.2.3 | d 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, the SOAP advisory explains how to limit iContr |
From the original article
4 min read at thehackernews.com
Six critical vulnerabilities in F5 BIG-IP allow an attacker to crash the Traffic Management Microkernel (TMM) without logging in, disrupting traffic until the TMM restarts. Each flaw 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. F5, which makes BIG-IP, disclosed the flaws today and says they
thehackernews.com
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.