Subscribe
Cybersecurity

F5 ships emergency hotfixes for six critical BIG-IP flaws, no workaround

Sunday, November 22, 2026 · 5 min read

F5 released emergency hotfixes on Nov 18 for six critical BIG-IP flaws, all rated CVSS 9.8, with no workaround — patching is the only fix. Coverage followed on Nov 20.

Bearish$FFIV

📊 Scorecard: our Bearish call on $FFIV is scored from $303.99, the last close before it ran. Its first result comes after the next close.

F5 ships emergency hotfixes for six critical BIG-IP flaws, no workaround

The News

F5 released out-of-band engineering hotfixes for six critical BIG-IP vulnerabilities that let unauthenticated attackers crash the Traffic Management Microkernel (TMM) and, F5 says, may allow remote code execution. The advisory was published Nov 18, with coverage following on Nov 20. Five are stack-based buffer overflows in iRules — CVE-2026-120285 (PSC::ip_address), CVE-2026-120292 (MR::message route), CVE-2026-116953 (GENERICMESSAGE::route), CVE-2026-120722 (DNS::scrape) and CVE-2026-121805 (PEM::subscriber) — and the sixth is CVE-2026-123637, a stack-based buffer overflow in BIG-IP Access Policy Manager affecting virtual servers whose per-request policy combines the Client Information and Endpoint Security agents. All six are CVSS 9.8 under CVSS v3.1 (9.3 under CVSS v4.0).

A seventh flaw, CVE-2026-126822 (CVSS 8.7), is a high-severity integer underflow in BIG-IP APM SAML enabling unauthenticated denial-of-service. F5 lists no workaround for any of the six critical flaws — patching is the only fix, and the correct hotfix depends on the exact installed build. Affected: BIG-IP 17.1.0–17.1.3, 17.5.0–17.5.1 and 21.1.0, plus BIG-IP Next for Kubernetes 2.2–2.4 and BIG-IP CNF — though CVE-2026-120722 (DNS::scrape) affects BIG-IP DNS only, not all BIG-IP modules, and F5's advisory lists BIG-IP CNF as not vulnerable for that CVE even though its CVE record lists CNF as affected.

F5 has not reported any known exploitation in the wild, but notes cybercrime and nation-state groups have often abused F5 vulnerabilities — most recently a critical BIG-IP APM flaw (CVE-2026-94127) actively exploited as a zero-day in September. This is a different set of flaws from the F5 NGINX fixes filed on Nov 19 (NGINX2Root, CVE-2026-123007/123633) — a different product and different CVEs from the same Nov 18 advisory batch. The RCE path here is F5's "may allow", not a demonstrated exploit.

Six flaws, all 9.8, no workaround — the only fix is a patch, and the right patch depends on your exact build.

Why It Matters

This matters because BIG-IP sits in front of the applications it protects. It decides which server handles each request and enforces the security policies around it — so a flaw in BIG-IP is not a flaw in one app, it is a flaw in the gate in front of many apps. An unauthenticated attacker, meaning one with no login at all, can crash the Traffic Management Microkernel that does the core work, and F5 says the flaws may allow remote code execution. RCE is F5's "may allow", not a demonstrated exploit — but the possibility is why the score is 9.8.

The no-workaround line is the second problem. With most flaws there is a temporary mitigation — turn a feature off, block a pattern, restrict access — while the patch is tested. Here there is none: patching is the only fix, and the correct hotfix depends on the exact installed build, so every customer has to match patch to build and roll it out under pressure. Affected versions span BIG-IP 17.1.0–17.1.3, 17.5.0–17.5.1 and 21.1.0, plus BIG-IP Next for Kubernetes 2.2–2.4 and BIG-IP CNF — a wide footprint.

The third problem is the precedent. F5 itself notes that cybercrime and nation-state groups have often abused its vulnerabilities, and the most recent example is fresh: a critical BIG-IP APM flaw, CVE-2026-94127, was actively exploited as a zero-day in September. That history is why the absence of known exploitation today is thin comfort — the advisory is public, the flaws are described, and attackers now have a shopping list. The September case is the model for what the next few days could look like if patching lags.

Analyst's Take

Our call is Bearish. Six unauthenticated flaws, all rated 9.8, with no workaround and a possible path to remote code execution is about as bad as a vulnerability advisory gets — and the September precedent, when a critical BIG-IP APM flaw was actively exploited as a zero-day, shows what happens next when patches are slow. The only good news is that F5 has reported no known exploitation in the wild yet.

What to watch next is the patching clock. The correct hotfix depends on the exact installed build, which makes this a fiddly rollout rather than a single click — and every unpatched BIG-IP box is now a known target, since the advisory itself describes the flaws in detail. Watch for exploitation reports in the coming days: the window between advisory and active abuse is the metric that matters, and September's zero-day suggests it can be short.

For investors, the tension is visible in the price. F5 closed Friday at $303.99, down 4.43%, in a session when most of the market fell — the stock fell with the rout, so the price gives no comfort that the market is shrugging off the flaws. But the bearish call here is about the product, not the share price: a vendor whose flagship product needs six emergency 9.8 patches at once, with no workaround, is a vendor whose customers are about to spend a difficult week patching — and whose track record, per F5's own note, includes nation-state groups abusing its flaws. Reader poll: Have you patched BIG-IP yet — yes or no? Vote: Patched already, Patching today, Not affected.

Are you bullish or bearish on this story?

By The Numbers

6Critical BIG-IP flaws, all CVSS 9.8
9.8CVSS v3.1 score for each of the six critical flaws
0Workarounds listed for any of the six critical flaws
Nov 18Advisory published; Nov 20 coverage
8.7CVSS score of the seventh, high-severity flaw
$303.99F5 close on Friday, down 4.43%

FAQ

What is BIG-IP?

BIG-IP is F5's family of products that manage and protect the traffic flowing into websites and apps — deciding which server handles each request, encrypting connections, and enforcing security policies. It sits in front of the applications it protects, so a flaw in it can expose everything behind it.

What is a buffer overflow?

A buffer overflow is a flaw where a program writes more data into a fixed-size memory space than fits, spilling over into neighbouring memory. Attackers can use that spill to crash the program or, in the worst case, run their own code. All six critical flaws here are stack-based buffer overflows.

What is an out-of-band hotfix?

An out-of-band hotfix is an emergency patch released outside the normal update schedule, because the flaws are too serious to wait. F5 released these hotfixes on Nov 18 rather than holding them for the next planned release — and with no workaround available, patching is the only way to close them.

What is RCE?

RCE stands for remote code execution: an attacker running their own code on a target machine from a distance, without needing a login. F5 says these flaws may allow RCE — that is F5's wording, not a demonstrated exploit — but the possibility alone is why all six score 9.8 out of 10.

👁

Source: BleepingComputer

Get the daily briefing. AI news with a markets lens — tickers, bullish/bearish reads, zero hype. Subscribe free on Substack

More on $FFIV

All $FFIV coverage →

More from AI Agent Update