F5 disclosed a critical stack-based buffer overflow in BIG-IP Access Policy Manager (APM) on November 18, 2026. Tracked as CVE-2026-123637, the flaw allows a remote, unauthenticated attacker to terminate the Traffic Management Microkernel (TMM), interrupting traffic while the process restarts.
The affected configuration requires APM provisioning and a virtual server with a per-request policy that includes both the Client Information agent and the Endpoint Security agents.
F5 says the memory corruption may also enable remote code execution (RCE). The advisory rates the flaw 9.8 under CVSS v3.1 and 9.3 under CVSS v4.0.
Critical F5 BIG-IP Stack Buffer Overflow Flaw
The flaw resides in the data plane, which handles application traffic, rather than the control plane. Restricting management-interface access does not remove exposure on an affected virtual server.
The policy prerequisites distinguish this issue from the separate BIG-IP APM remote code execution flaw tracked as CVE-2026-94127. F5 classified the defect as CWE-121, an out-of-bounds write to a stack-allocated buffer, and assigned it internal tracking ID 2567577.
A TMM crash accounts for the denial-of-service impact, but a restart alone does not establish that an attacker executed code. F5 did not disclose the requests that triggered it.
The separate BIG-IP HTTP/2 denial-of-service flaw also affected the data plane but involved a different traffic-processing component.
Affected releases and engineering hotfixes
F5 lists BIG-IP APM 21.1.0, 17.5.0 through 17.5.1, and 17.1.0 through 17.1.3 as affected. Other BIG-IP modules, BIG-IP CNF, BIG-IP Next for Kubernetes, BIG-IQ Centralized Management, F5 Insight, F5OS, and NGINX are listed as unaffected.
F5 did not evaluate releases that have reached End of Technical Support. The PoisonedRefresh campaign targeting BIG-IP APM involved CVE-2025-53521 and does not establish active exploitation of this flaw.
F5’s hotfix guidance, K000164239, maps each engineering build to the currently installed base release or engineering hotfix. The two builds listed for each 17.x release line are not interchangeable; administrators should verify the full installed build string before selecting a package.
| Affected BIG-IP APM releases | Current base release or engineering build | Engineering hotfix |
|---|---|---|
| 21.1.0 | 21.1.0.4 base release or earlier in the release line | BIGIP-21.1.0.4.0.19.3-ENG |
| 17.5.0–17.5.1 | BIGIP-17.5.1.10.0.7.35-ENG or BIGIP-17.5.1.10.0.37.35-ENG | BIGIP-17.5.1.10.0.80.35-ENG |
| 17.5.0–17.5.1 | 17.5.1.11 base release or earlier in the release line | BIGIP-17.5.1.11.0.61.12-ENG |
| 17.1.0–17.1.3 | BIGIP-17.1.3.6.0.9.20-ENG | BIGIP-17.1.3.6.0.14.20-ENG |
| 17.1.0–17.1.3 | 17.1.3.7 base release or earlier in the release line | BIGIP-17.1.3.7.0.21.4-ENG |
F5 lists no workaround and directs customers to obtain the applicable package from MyF5 Downloads. Administrators should inventory virtual servers with the affected policy configuration and prioritize those reachable from untrusted networks.
Customers running a custom engineering hotfix should request a replacement build from F5 Support. Because engineering hotfixes undergo less extensive quality assurance than scheduled releases, operators should verify the installed build and test traffic handling and APM policy behavior after deployment.
Join 16,000+ SOC teams using ANY.RUN to streamline threat investigations and reduce manual effort. Explore for your team

