F5 discloses six critical BIG-IP flaws that can crash traffic
Each flaw needs a specific iRule or APM setup; F5 offers only engineering hotfixes and lists no workaround.
TMM crash DoS in F5 BIG-IP APM when policytrace is on
When BIG-IP APM is provisioned, a virtual server has an APM access profile and a per-request policy, and the tmm.access.policytrace key is enabled, undisclosed requests can terminate the Traffic Management Microkernel. A remote unauthenticated attacker can cause a data-plane denial of service; traffic stops until TMM restarts. There is no control-plane exposure. The key is disabled by default. End-of-support versions were not evaluated.
What to do: Apply F5's update for CVE-2026-121812. The crash requires tmm.access.policytrace, which is disabled by default.
| Product | Affected |
|---|---|
| F5 BIG-IP APM | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description: When BIG-IP APM is provisioned, and a virtual server is configured with an APM access profile and a per-request policy, and the tmm.access.policytrace database key is enabled, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate. The key is disabled by default. Impact: 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 . There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Each flaw needs a specific iRule or APM setup; F5 offers only engineering hotfixes and lists no workaround.
Today 966 readers · 1.1K views · 90 reads · all time 211K views