F5 has released engineering hotfixes for five critical BIG-IP vulnerabilities. Remote attackers without an account can crash traffic processing and may execute code when particular rules or access policies are configured. Check the deployed traffic configuration and install the hotfix that matches the existing build.

F5 calls these data-plane issues, affecting the software that handles client traffic. Its advisories explicitly say there is no control-plane exposure through these flaws. Restricting the administrative interface alone therefore does not remove the described attack paths.

Evidence status: vendor-confirmed vulnerabilities; the reviewed reporting identifies no in-the-wild exploitation of these five flaws. Earlier attacks against other F5 vulnerabilities do not establish exploitation of this batch.

Exposure depends on the configured traffic path

BIG-IP fronts applications and applies traffic and access rules. An iRule is a script controlling how it handles traffic. APM, Access Policy Manager, supplies access-control policies. F5 names these conditions:

Vulnerability Required configuration named by F5
CVE-2026-121805 A virtual server uses an iRule processing client traffic with PEM::subscriber. The BIG-IP module affected is Policy Enforcement Manager.
CVE-2026-120292 A virtual server has an HTTP profile and an iRule using MR::message route.
CVE-2026-120285 A virtual server has an HTTP profile and an iRule containing PSC::ip_address.
CVE-2026-116953 A virtual server uses an iRule processing client traffic with GENERICMESSAGE::route.
CVE-2026-123637 APM is provisioned, and the applied per-request policy includes Client Information and Endpoint Security agents.

For each, F5 describes a stack-based buffer overflow in the Traffic Management Microkernel, its traffic-processing engine. A crash interrupts traffic while that process restarts. The vendor describes code execution as a possible consequence, rather than a documented compromise of every affected appliance.

The advisories list BIG-IP 21.1.0, 17.5.0–17.5.1 and 17.1.0–17.1.3 within their affected module ranges. A matching version still needs the corresponding feature configuration. F5 evaluates supported releases; an omitted end-of-support version is not a safety finding.

Choose the exact engineering hotfix

F5’s November 18 notification predates BleepingComputer’s November 20 report. Its separate hotfix-selection guidance gives these paths:

Current installation Engineering hotfix
BIGIP-17.1.3.6.0.9.20-ENG BIGIP-17.1.3.6.0.14.20-ENG
17.1.3.7 base release or an earlier base release in that line BIGIP-17.1.3.7.0.21.4-ENG
BIGIP-17.5.1.10.0.7.35-ENG or BIG-IP-17.5.1.10.0.37.35-ENG BIGIP-17.5.1.10.0.80.35-ENG
17.5.1.11 base release or an earlier base release in that line BIGIP-17.5.1.11.0.61.12-ENG
21.1.0.4 base release or an earlier base release in that line BIGIP-21.1.0.4.0.19.3-ENG

Those identifiers reproduce F5’s selection document, including its differently spelled BIG-IP- entry. Custom engineering-hotfix users should contact F5 Support for a replacement build. Do not select an image by a shortened version number alone.

The four iRule advisories also list affected CNF and Next for Kubernetes branches: 2.2.0–2.2.5, 2.3.0–2.3.4 and 2.4.0–2.4.2. They name 2.2.5-EHF1, 2.3.4-EHF1 and 2.4.2-EHF1 as the corresponding repairs. These have a separate distribution path; the TMOS image table above is not their upgrade procedure.

F5 lists no mitigation for the five critical flaws. Review the feature-specific advisories, preserve a tested recovery path and verify the installed hotfix after maintenance. Engineering hotfixes receive less extensive quality assurance than scheduled releases, which makes compatibility planning important alongside prompt deployment.

Keep the separate SAML crash flaw distinct

The same batch includes CVE-2026-126822, a high-severity APM denial-of-service flaw. It requires a virtual server configured as a SAML service provider, accepting federated sign-ins. F5 does not describe code execution for this flaw.

Unlike the five critical advisories, this one supplies a mitigation: remove the SAML Auth agent if that functionality is unnecessary, and restrict the affected virtual server to trusted client networks. That advice does not substitute for repairing the other traffic-processing paths.

Caveat: Internet fingerprint counts do not show which systems have the required policies or remain unpatched; F5 supplies the configuration and repair assessment.