CVE-2026-125272: F5 BIG-IP APM: unauthenticated TMM crash causes DoS
HIGHCVE-2026-125272 is a stack-based buffer overflow (CWE-121) in F5 BIG-IP APM that lets a remote, unauthenticated attacker send crafted requests to a virtual server with a per-request policy containing a form-based Logon Page and crash the Traffic Management Microkernel (TMM). This is a network appliance flaw, not an AI/ML package flaw, and our records show no affected AI packages, no tracked downstream dependents, and no AI-specific attack surface. The vulnerability is rated High (CVSS 7.5, availability impact only) and requires no privileges or user interaction. It is not in CISA KEV, no public exploit or Nuclei template is known, and EPSS data is not yet available, so there is no evidence of active exploitation today. It matters for AI environments mainly where BIG-IP fronts AI gateways, inference APIs, or SSO portals, because a TMM restart interrupts all traffic through that device. Review F5 advisory K000163938, identify BIG-IP APM instances with form-based Logon Page per-request policies, and apply the fixed software version. Versions past End of Technical Support are not evaluated, so confirm your release is still supported.
What is the risk?
Moderate overall risk. Exploitability is high (network vector, low complexity, no authentication, no user interaction), but impact is limited to availability, with no confidentiality or integrity loss. There is no known public exploit, no KEV listing, and EPSS is unavailable, so exploitation likelihood is unquantified. Exposure is limited to BIG-IP systems licensed and provisioned with APM and configured with a per-request policy that includes a form-based Logon Page. The issue affects the data plane only; the control plane is not exposed. The AI/ML relevance is indirect: it applies only where BIG-IP sits in front of AI services.
How does the attack unfold?
How severe is it?
What is the attack surface?
What should I do?
1 step1) Read F5 advisory K000163938 and upgrade to the fixed BIG-IP version it lists. 2) Inventory devices with APM provisioned and per-request policies containing a form-based Logon Page. 3) Where patching is delayed, follow any F5 mitigation in the advisory and restrict access to affected virtual servers to trusted networks. 4) Monitor for unexpected TMM restarts or core files, and alert on repeated restarts. 5) Make sure high-availability failover is configured and tested so a single TMM crash does not cause a full outage. 6) Check that your software release is within support, since EoTS versions were not evaluated.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-125272?
CVE-2026-125272 is a stack-based buffer overflow (CWE-121) in F5 BIG-IP APM that lets a remote, unauthenticated attacker send crafted requests to a virtual server with a per-request policy containing a form-based Logon Page and crash the Traffic Management Microkernel (TMM). This is a network appliance flaw, not an AI/ML package flaw, and our records show no affected AI packages, no tracked downstream dependents, and no AI-specific attack surface. The vulnerability is rated High (CVSS 7.5, availability impact only) and requires no privileges or user interaction. It is not in CISA KEV, no public exploit or Nuclei template is known, and EPSS data is not yet available, so there is no evidence of active exploitation today. It matters for AI environments mainly where BIG-IP fronts AI gateways, inference APIs, or SSO portals, because a TMM restart interrupts all traffic through that device. Review F5 advisory K000163938, identify BIG-IP APM instances with form-based Logon Page per-request policies, and apply the fixed software version. Versions past End of Technical Support are not evaluated, so confirm your release is still supported.
Is CVE-2026-125272 actively exploited?
No confirmed active exploitation of CVE-2026-125272 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-125272?
1) Read F5 advisory K000163938 and upgrade to the fixed BIG-IP version it lists. 2) Inventory devices with APM provisioned and per-request policies containing a form-based Logon Page. 3) Where patching is delayed, follow any F5 mitigation in the advisory and restrict access to affected virtual servers to trusted networks. 4) Monitor for unexpected TMM restarts or core files, and alert on repeated restarts. 5) Make sure high-availability failover is configured and tested so a single TMM crash does not cause a full outage. 6) Check that your software release is within support, since EoTS versions were not evaluated.
What systems are affected by CVE-2026-125272?
This vulnerability affects the following AI/ML architecture patterns: Model serving behind BIG-IP gateways, AI application access portals, Network edge and load balancing for AI services.
What is the CVSS score for CVE-2026-125272?
CVE-2026-125272 has a CVSS v3.1 base score of 7.5 (HIGH).
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0029Denial of AI ServiceAML.T0049Exploit Public-Facing ApplicationCompliance Controls Affected
What are the technical details?
Original Advisory
Description: When BIG-IP APM is licensed and provisioned, and a virtual server with the APM access profile is configured with a per-request policy containing a form-based Logon Page, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate. 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.
Exploitation Scenario
An attacker finds an internet-facing BIG-IP virtual server with an APM access profile that publishes an AI platform portal, such as an internal LLM gateway or MLOps console, behind a form-based logon page. They send crafted requests to that endpoint, which overflow a stack buffer and crash TMM. Traffic to the AI services drops until TMM restarts, and repeated requests keep the service down. This disrupts inference APIs and user access without any authentication or access to the AI systems themselves.
Weaknesses (CWE)
CWE-121 — Stack-based Buffer Overflow: The product writes past the end of a buffer that was allocated on the stack.
- [Operation, Build and Compilation] Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- [Architecture and Design] Use an abstraction library to abstract away risky APIs. Not a complete solution.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
Timeline
Related Vulnerabilities
CVE-2026-3366010.0TensorFlow: type confusion NPD in tensor conversion
Same attack type: DoSCVE-2023-256689.8TensorFlow: unauthenticated RCE via heap buffer overflow
Same attack type: DoSCVE-2022-235879.8TensorFlow: integer overflow in Grappler enables RCE
Same attack type: DoSCVE-2022-359399.8TensorFlow: ScatterNd OOB write enables RCE/crash
Same attack type: DoSCVE-2022-419009.8TensorFlow: heap OOB RCE in FractionalMaxPool op
Same attack type: DoS