Skip to content
[HIGH] Vulnerabilities #vulnerabilities

F5 Releases Patches for Five Critical BIG-IP Vulnerabilities

By Rockstar Media Editorial Original report: BleepingComputer ↗

$ grep -o 'CVE-[0-9-]*'

┌─ f5-patches-big-ip-rce-flaws.md :: hero

Illustrative stock photo for: F5 Releases Patches for Five Critical BIG-IP Vulnerabilities
Illustrative stock photo for: F5 Releases Patches for Five Critical BIG-IP Vulnerabilities Photo by Rashed Paykary on Pexels

F5 has issued emergency out-of-band patches for five critical-severity vulnerabilities and one high-severity flaw affecting its BIG-IP networking and access management products. The five critical stack-based buffer overflow flaws affect BIG-IP Access Policy Manager (APM) and BIG-IP iRules, allowing remote, unauthenticated attackers to trigger denial-of-service or achieve remote code execution. A sixth high-severity flaw affects BIG-IP APM SAML and enables remote denial-of-service attacks. With F5 serving more than 23,000 customers worldwide, these updates are relevant to organisations in Malaysia operating BIG-IP appliances.

Key Facts

Attribute Value
Affected products BIG-IP Access Policy Manager (APM), BIG-IP iRules, and BIG-IP APM SAML
CVE IDs CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953, CVE-2026-123637 (critical); CVE-2026-126822 (high)
Exploited in the wild Not flagged by F5 as exploited in attacks

What Do the F5 BIG-IP Vulnerabilities Affect?

Five critical stack-based buffer overflow vulnerabilities affect BIG-IP Access Policy Manager (APM) and the BIG-IP iRules programmable scripting feature, enabling unauthenticated attackers to terminate the Traffic Management Microkernel (TMM) and execute arbitrary code. A separate high-severity integer underflow flaw affects BIG-IP APM SAML, allowing remote denial-of-service attacks.

The five critical stack-based buffer overflow flaws are tracked as CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953, and CVE-2026-123637. They affect F5's BIG-IP APM centralised access management proxy solution and BIG-IP iRules on systems with vulnerable configurations. In addition, F5 released engineering hotfixes for CVE-2026-126822, a high-severity BIG-IP APM SAML vulnerability caused by an integer underflow (wrap or wraparound) weakness that remote, unauthenticated threat actors can abuse in denial-of-service (DoS) attacks.

"Traffic is disrupted while the TMM process restarts. This vulnerability allows a remote unauthenticated attacker to cause a denial-of-service (DoS) on the BIG-IP system and may perform RCE. There is no control plane exposure; this is a data plane issue only."

F5

F5 confirmed there are no mitigation measures for these flaws and advised security teams to install the out-of-band hotfixes released on Wednesday.

Are the Vulnerabilities Being Exploited in Attacks?

F5 has not flagged any of these newly patched vulnerabilities as exploited in attacks. However, internet threat watchdog Shadowserver currently tracks more than 177,000 BIG-IP instances and over 14,600 IP addresses with BIG-IP APM fingerprints online, and both cybercrime and nation-state groups have often abused F5 vulnerabilities.

Shadowserver noted there is no information on how many of the internet-exposed BIG-IP instances are honeypots or have already been patched against these issues. In recent years, attackers have targeted F5 security flaws to breach corporate networks, map internal servers, hijack devices, deploy data-wiping malware, and steal sensitive files from victims worldwide. The US Cybersecurity and Infrastructure Security Agency (CISA) has flagged seven F5 vulnerabilities as actively exploited since November 2021, four of which have also been used by ransomware gangs. In September, F5 patched another critical BIG-IP APM vulnerability (CVE-2026-94127) that is being actively exploited in zero-day remote code execution attacks, following an August 2025 breach in which state-backed hackers stole F5 source code and information on undisclosed BIG-IP vulnerabilities.

Since November 2021, CISA has flagged seven F5 vulnerabilities as actively exploited, including four used by ransomware gangs.

What Should You Do?

  • Install F5's out-of-band hotfixes and engineering hotfixes released on Wednesday, and upgrade BIG-IP systems to the latest official version as soon as possible.
  • Do not rely on configuration workarounds, as F5 confirmed there are no mitigation measures for these vulnerabilities.
  • Review internet-facing BIG-IP, BIG-IP APM, and BIG-IP iRules deployments to confirm whether patches have been applied.
  • Monitor BIG-IP systems for unexpected TMM restarts or suspicious activity, and report suspected cybersecurity incidents in Malaysia to Cyber999 (MyCERT).

Common Questions

Do these vulnerabilities affect the BIG-IP control plane?

No. F5 stated there is no control plane exposure and described the issue as a data plane vulnerability only. However, exploiting the flaws on vulnerable configurations can terminate the Traffic Management Microkernel process, disrupt traffic while it restarts, and potentially enable remote code execution.

Are temporary workarounds or mitigations available before patching?

No. F5 stated that it has no mitigation measures for these vulnerabilities. Security teams running affected BIG-IP Access Policy Manager or BIG-IP iRules configurations are advised to install the out-of-band hotfixes released on Wednesday and upgrade systems to the latest version promptly.

How many BIG-IP devices are currently exposed online?

According to internet threat watchdog Shadowserver, more than 177,000 BIG-IP instances and over 14,600 IP addresses with BIG-IP APM fingerprints are currently exposed online. There is no available information on how many of these exposed systems are honeypots or have already been patched.

Sources and Methodology

This dispatch is based solely on reporting from BleepingComputer, published on November 20, 2026. No external vendor advisories, technical bulletins, or third-party documents were independently reviewed or verified in preparing this summary.

$ ls ./tags

  • #Vulnerabilities

From the network