Unauthenticated TMM termination via undisclosed SSL traffic
Published May 13, 2026 · Updated May 13, 2026
Incorrect buffer-size calculation in F5 BIG-IP products allows remote attackers to terminate TMM with undisclosed SSL/TLS traffic. F5 identifies the Traffic Management Microkernel as the failing component but has not disclosed the calculation or traffic pattern that triggers it. Reachability requires an SSL-enabled virtual server on VE without QAT or hardware with crypto.hwacceleration disabled; successful exploitation interrupts traffic processing.
Summary
What happened
Incorrect buffer-size calculation in F5 BIG-IP products allows remote attackers to terminate TMM with undisclosed SSL/TLS traffic. F5 identifies the Traffic Management Microkernel as the failing component but has not disclosed the calculation or traffic pattern that triggers it. Reachability requires an SSL-enabled virtual server on VE without QAT or hardware with crypto.hwacceleration disabled; successful exploitation interrupts traffic processing.
The record
- CVE
- CVE-2026-40618
- Published
- May 13, 2026
- Updated
- May 13, 2026
- Vendor
- F5 Networks
- Product
- BIG-IP Next for Kubernetes
- Classifications
- CWE-131, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- May 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <2.2.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo