Skip to content
Brief Security & Trust ·

F5 warns of six critical BIG-IP flaws that can crash traffic in set-ups

The risk sits in custom iRule and APM settings, and F5's only fix is engineering hotfixes.

In brief
  • Five of six critical BIG-IP flaws sit in iRules, a feature administrators use to manage traffic. The sixth is in the APM module.
  • F5 offers only engineering hotfixes and no workaround. Its advisories do not say anyone has exploited the flaws.

F5 announced on November 18, 2026 that six critical flaws affect BIG-IP, its traffic-handling product, The Hacker News reported. An attacker who has not logged in could crash the Traffic Management Microkernel (TMM), the process that handles almost all BIG-IP network traffic. Traffic is disrupted until TMM restarts. F5 says the flaws may also allow remote code execution, meaning the attacker runs their own code. Each scores 9.8 on the CVSS v3.1 severity scale, which tops out at 10.

The Hacker News describes each flaw as a stack-based buffer overflow. In plain terms, input overruns a fixed block of memory. A flaw can be reached only when a particular iRule command or APM policy agent handles that input. iRules are a feature administrators use to manage traffic. Five of the six flaws sit in iRules, and one sits in APM. None of F5's advisories says anyone has exploited them. F5 lists no workaround, and its only fixes are engineering hotfixes.

The risk sits in settings your own team wrote, and the only fix is code F5 says gets less testing than scheduled releases. F5's hotfix policy promises no warranty. Leaders can ask three questions. Which virtual servers use these commands or agents? Is a custom hotfix already installed, which needs a new one from F5 support? What is the rollback plan if a hotfix misbehaves?

A WebPulse Brief: a short report of an important event, written by the WebPulse Newsroom with AI assistance and checked against the reporting below. When there is more to explain, we follow up with a full story. How we use AI.

Reporting: F5.