Skip to content
[ SIGNAL VERIFIED ] INDEPENDENT CYBERCRIME JOURNALISMCLASSIFIED // THE UNDERGROUND HAS A NEWSROOM / RSS
.COM
Latest News
ALL NEWS
Newsroom

F5 Issues Emergency BIG-IP Fixes for Six Critical Traffic-Processing Flaws

F5's out-of-band November advisories describe six critical BIG-IP issues affecting specific virtual-server configurations, with engineering hotfixes.

F5 Issues Emergency BIG-IP Fixes for Six Critical Traffic-Processing Flaws
PUBLISHED UPDATED November 20, 2026 at 1:49 PM EST

Updated November 20 — identify the exact F5 advisory and fix, not a generic BIG-IP patch

New technical reporting clarifies the affected F5 components and correction process. Five prominently discussed critical issues involve BIG-IP iRules or Access Policy Manager: CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953 and CVE-2026-123637. Canada’s Cyber Centre additionally lists CVE-2026-120722 among the November 18 out-of-band notices. These are configuration-dependent traffic-processing vulnerabilities, not uniform proof that every BIG-IP deployment is remotely exploitable. A separate high-severity APM SAML issue, CVE-2026-126822, is also covered in November 20 reporting; it should not be conflated with the critical buffer-overflow issues.

F5 has published engineering hotfixes for affected BIG-IP releases and corresponding fixes for certain cloud-native lines. The Canadian advisory identifies specific fixed build strings for BIG-IP 17.1, 17.5 and 21.1 and for BIG-IP CNF/Next for Kubernetes. Administrators should match their exact product and branch to the vendor’s bulletin rather than assume a shared number applies to all devices. F5 has not confirmed active exploitation of these new issues in the reviewed advisories. Incident responders should distinguish the documented potential for denial of service or code execution from a verified compromise.

Sources: Canadian Centre for Cyber Security, AV26-1178 (Nov. 19); BleepingComputer, November 20; F5 out-of-band bulletin index.

IPCRIME NEWSROOM | NOVEMBER 19, 2026

F5 issued an out-of-band security notification on November 18 addressing a cluster of critical vulnerabilities affecting BIG-IP traffic handling. National cyber authorities and industry responders elevated the advisories on November 19, warning that certain reachable virtual-server configurations could permit unauthenticated disruption and, for several flaws, possible code execution.

Which features matter

The disclosures center on the Traffic Management Microkernel, which processes application traffic. Particular iRule commands or Access Policy Manager per-request policy configurations are involved. F5’s advisories include CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953, CVE-2026-123637 and another related traffic-processing issue. It is not accurate to say that every BIG-IP configuration has the same exposure.

Impact and current status

Several flaws carry a CVSS v3.1 rating of 9.8, with possible remote denial of service and remote code execution under specific conditions. F5 provides engineering hotfixes for affected BIG-IP lines; it does not list a universal configuration workaround. Health-ISAC said there had been no reported exploitation when it issued its November 19 bulletin.

Appliance and cloud-native deployments

Canada’s Cyber Centre includes BIG-IP 17.1, 17.5 and 21.1 lines as well as selected BIG-IP CNF and BIG-IP Next for Kubernetes builds in its November 19 alert. The fix depends on product branch, so operators need the matching engineering release rather than a guess based on a shared product name.

IPCRIME’s priority sequence

Inventory BIG-IP instances and the iRules or APM policies actually attached to internet-facing virtual servers. Compare each device with F5’s product-specific advisory, arrange the appropriate engineering hotfix through its supported channel, validate traffic handling afterward, and inspect operational logs if unusual crashes occurred before patching. A public vulnerability notice should not be described as a confirmed breach of your appliance.

Source documentation

Reporting based on the documents linked above. The featured image is conceptual IPCRIME artwork, not a photograph of the described incident.

Editorial note

IPCRIME distinguishes public records and documented findings from allegations, analysis and commentary. Report corrections through our contact page.