Traefik up to 2.11.55/3.7.11 HTTP/3 entrypoints resource consumption

Summaryinfo

A vulnerability marked as problematic has been reported in Traefik up to 2.11.55/3.7.11. The affected element is an unknown function of the component HTTP/3 entrypoints. This manipulation causes resource consumption. This vulnerability appears as CVE-2026-88012. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Traefik up to 2.11.55/3.7.11 and classified as problematic. Affected by this vulnerability is an unknown code of the component HTTP/3 entrypoints. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:

Traefik is an open source HTTP reverse proxy and load balancer. From 2.8.2 until 2.11.56 and 3.7.12, HTTP/3 entrypoints do not apply entryPoints..transport.respondingTimeouts.readTimeout because the timeout is enforced on a TCP connection and the HTTP/3 server has no corresponding QUIC stream deadline. An unauthenticated client can use a slow request body, trickling data indefinitely while holding a request and an upstream connection open and exhausting backends with bounded connection pools. This issue is fixed in 2.11.56 and 3.7.12.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-88012 since 09/09/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

Upgrading to version 2.11.56 or 3.7.12 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Traefik

Version

• 2.11.0
• 2.11.1
• 2.11.2
• 2.11.3
• 2.11.4
• 2.11.5
• 2.11.6
• 2.11.7
• 2.11.8
• 2.11.9
• 2.11.10
• 2.11.11
• 2.11.12
• 2.11.13
• 2.11.14
• 2.11.15
• 2.11.16
• 2.11.17
• 2.11.18
• 2.11.19
• 2.11.20
• 2.11.21
• 2.11.22
• 2.11.23
• 2.11.24
• 2.11.25
• 2.11.26
• 2.11.27
• 2.11.28
• 2.11.29
• 2.11.30
• 2.11.31
• 2.11.32
• 2.11.33
• 2.11.34
• 2.11.35
• 2.11.36
• 2.11.37
• 2.11.38
• 2.11.39
• 2.11.40
• 2.11.41
• 2.11.42
• 2.11.43
• 2.11.44
• 2.11.45
• 2.11.46
• 2.11.47
• 2.11.48
• 2.11.49
• 2.11.50
• 2.11.51
• 2.11.52
• 2.11.53
• 2.11.54
• 2.11.55
• 3.7.0
• 3.7.1
• 3.7.2
• 3.7.3
• 3.7.4
• 3.7.5
• 3.7.6
• 3.7.7
• 3.7.8
• 3.7.9
• 3.7.10
• 3.7.11

Website

• Product: https://github.com/traefik/traefik/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion