github.com/traefik/traefik/v3
Affected
- introduced
0, fixed3.6.7(semver)
Fixed versions
3.6.7
Fix
- Fixed version
3.6.7go get github.com/traefik/traefik/[email protected]
Advisory
Also known as: CVE-2026-22045, GO-2026-4322
Traefik's ACME TLS-ALPN fast path lacks timeouts and close on handshake stall
Impact
There is a potential vulnerability in Traefik ACME TLS certificates' automatic generation: the ACME TLS-ALPN fast path can allow unauthenticated clients to tie up goroutines and file descriptors indefinitely when the ACME TLS challenge is enabled.
A malicious client can open many connections, send a minimal ClientHello with acme-tls/1, then stop responding, leading to denial of service of the entrypoint.
Patches
For more information
If you have any questions or comments about this advisory, please open an issue.
<details>
<summary>Original Description</summary>
\[Security\] ACME TLS-ALPN fast path lacks timeouts and close on handshake stall
Dear Traefik security team,
We believe we have identified a resource-exhaustion issue in the ACME TLS-ALPN fast path that can allow unauthenticated clients to tie up goroutines and file descriptors indefinitely when the ACME TLS challenge is enabled.
Summary
pkg/server/router/tcp/router.go (ACME TLS-ALPN handling). acme-tls/1, Traefik intercepts it and calls tls.Server(...).Handshake() without any read/write deadlines and without closing the connection afterward. Relevant snippets
// Deadlines are cleared before protocol dispatch
if err := conn.SetDeadline(time.Time{}); err != nil {
log.Error().Err(err).Msg("Error while setting deadline")
}
// ACME TLS-ALPN fast path
if !r.acmeTLSPassthrough && slices.Contains(hello.protos, tlsalpn01.ACMETLS1Protocol) {
r.acmeTLSALPNHandler().ServeTCP(r.GetConn(conn, hello.peeked))
return
}
// Handler invoked by the branch above
return tcp.HandlerFunc(func(conn tcp.WriteCloser) {
_ = tls.Server(conn, r.httpsTLSConfig).Handshake()
})
Impact
acme-tls/1, then stop responding, leading to denial of service of the entrypoint. http.Server timeouts; this bespoke path bypasses them.Conditions for exploitation
allowACMEByPass disabled for the entrypoint (the default when ACME TLS challenge is handled by Traefik).CWE
Proposed fix (illustrative)
@@ func (r *Router) acmeTLSALPNHandler() tcp.Handler {
- return tcp.HandlerFunc(func(conn tcp.WriteCloser) {
- _ = tls.Server(conn, r.httpsTLSConfig).Handshake()
- })
+ return tcp.HandlerFunc(func(conn tcp.WriteCloser) {
+ // Ensure the handshake cannot block indefinitely and always closes the socket.
+ _ = conn.SetReadDeadline(time.Now().Add(10 * time.Second))
+ _ = conn.SetWriteDeadline(time.Now().Add(10 * time.Second))
+
+ tlsConn := tls.Server(conn, r.httpsTLSConfig)
+ _ = tlsConn.Handshake()
+ _ = tlsConn.Close() // close regardless of handshake outcome
+ })
}
Alternatively, route ACME TLS-ALPN through the existing tcp.TLSHandler/HTTP server path so the configured timeouts and lifecycle management apply automatically.
CVSS v3.1 (estimate)
Please let us know if you would like a PoC or further details. We have not made any code changes in this report.
Let us know if you have any questions or need clarification\!
Best wishes,
Pavel Kohout
Aisle Research
</details>
Medium Basis: The source's own band: MODERATE
0, fixed 3.6.7 (semver)3.6.7
3.6.7go get github.com/traefik/traefik/[email protected]0, fixed 2.11.35 (semver)2.11.35
2.11.35go get github.com/traefik/traefik/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0