Hardware & ComponentsLOT 261122 · 3 min read

F5 patches five critical BIG-IP flaws rated 9.8 in NVD entries

F5 issued emergency hotfixes for five 9.8-rated BIG-IP flaws affecting iRules and APM. Shadowserver sees 177,000 exposed instances; F5 has not reported active exploitation.

By Nathan Brooks533 words

Key takeaways

  1. Five critical BIG-IP flaws were published on Nov. 18 and received emergency hotfixes.
  2. Each flaw has a CVSS v3.1 score of 9.8 and a CVSS v4.0 score of 9.3.
  3. Four flaws require specific iRules; one requires an APM per-request policy with two agents.
  4. Shadowserver tracks more than 177,000 exposed BIG-IP instances and more than 14,600 APM fingerprint addresses.
  5. F5 also patched five NGINX vulnerabilities after proof-of-concept exploits became public, SecurityWeek reported Nov. 19.
F5 releases emergency hotfixes for five critical BIG-IP flaws that can allow remote code execution
F5 releases emergency hotfixes for five critical BIG-IP flaws that can allow remote code execution — timwesterhoff / pixabay

By Nathan Brooks

F5 has released emergency hotfixes for five critical BIG-IP application delivery vulnerabilities, each rated 9.8 out of 10 under CVSS v3.1 and 9.3 under v4.0, according to National Vulnerability Database entries supplied by the company. Published on Wednesday, Nov. 18, the flaws can let remote, unauthenticated attackers crash BIG-IP’s traffic engine and possibly execute their own code.

F5 has not reported that the five flaws are being exploited, according to BleepingComputer. The company lists no mitigations and recommends installing the “out-of-band hotfixes,” the outlet said. F5 also states that there is “no control-plane exposure.”

None of the five is a universal remote trigger. Each needs a particular configuration on a virtual server, so the installation inventory matters as much as the patch download.

Which setups are exposed?

Four vulnerabilities sit in BIG-IP’s iRules traffic-scripting feature, while the fifth affects Access Policy Manager, or APM. The required conditions are specific:

  • CVE-2026-121805: An iRule using the PEM::subscriber command.
  • CVE-2026-120292: An HTTP profile and an iRule using MR::message route.
  • CVE-2026-120285: An HTTP profile and an iRule using PSC::ip_address.
  • CVE-2026-116953: An iRule using GENERICMESSAGE::route.
  • CVE-2026-123637: An APM per-request policy with the Client Information and Endpoint Security agents applied.

Crafted requests can terminate the Traffic Management Microkernel, or TMM, in every case, disrupting traffic while it restarts, and may lead to remote code execution. The vulnerable path therefore reaches the request-processing engine even though F5 reports no control-plane exposure.

How large is the visible exposure?

Shadowserver tracks more than 177,000 internet-exposed BIG-IP instances and more than 14,600 IP addresses showing APM fingerprints. The project cannot say how many of those systems are patched or are honeypots. Its dataset is an attack-surface directory, not a confirmed infection count.

A sixth BIG-IP flaw, CVE-2026-126822, carries a 7.5 rating. It lets attackers crash the TMM when APM is configured as a SAML service provider. F5 identifies this issue separately from the five emergency-rated vulnerabilities.

BIG-IP has been a frequent target in F5’s incident history. CISA has listed seven F5 flaws as actively exploited since November 2021, and F5 patched the APM zero-day CVE-2026-94127 in September. Those historical listings do not establish exploitation of the November vulnerabilities; F5 has said only that it has received no exploitation reports for these five bugs.

What did F5 fix outside BIG-IP?

Separately, F5 patched five NGINX vulnerabilities, a set dubbed NGINX2Root, during the same week after proof-of-concept exploits became public, SecurityWeek reported on Nov. 19. The NGINX updates are separate from the BIG-IP emergency fixes.

On Nov. 18, MLQ.ai reported on a decade-old NGINX HTTP/2 flaw that can let unauthenticated attackers run code. The source provided no individual CVE identifiers or scores for the five NGINX vulnerabilities.

For F5, the next test is how quickly operators patch a visible base exceeding 177,000 instances. Confirmed exploitation would turn five configuration-specific flaws into a broader outage and code-execution problem.

mlq.ai (Source)

Filed under

Share this article:

More from Nathan Brooks

Nathan Brooks

Show full bio

Senior reporter covering people, launches and day-to-day practice in Semiconductors, chip manufacturing, hardware, AI compute at Chip Dispatch.

1,201 articles

Read also

« Previous article