CVE-2026-114642·Traefik vulnerability
Traefik 2.11.0 before 2.11.58 and 3.0.0 before 3.7.14 stores its NTLM/Kerberos backend round tripper in a client-connection slot not keyed by ServersTransport, so one service's TLS client configuration is reused for another service's backend. An unauthenticated client can arm the slot via a backend issuing an NTLM or Negotiate challenge, then reach another service on the same keep-alive connection, bypassing its root CAs, server name, and certificate verification.
- Severity
- high
- Software
- Traefik
- Fixed in
- 3.7.14
- Published
Affected versions
From: 3.0.0
Until: 3.7.14
Fixed in: 3.7.14
How to fix this CVE
Upgrade Traefik immediately to version 2.11.58 or later (3.7.14+ for v3 deployments) to patch a critical TLS configuration bypass affecting NTLM and Kerberos authentication flows. This vulnerability allows attackers to reuse TLS client certificates and bypass certificate verification across different backend services on the same connection. Deploy the patched version and restart all Traefik instances to ensure the fix is active.
sudo dnf update traefikDefensia detects this vulnerability
What an exploitation attempt looks like
Sample log line indicative of exploitation attempts:
POST|GET .* HTTP/1\.1.*(?:WWW-Authenticate: Negotiate|WWW-Authenticate: NTLM).*Connection: keep-alive.*followed by request to different Host header on same connectionHow to check if you are affected
- Check installed Traefik version: traefik version or docker inspect $(docker ps -q -f ancestor=traefik) | grep -i version
- Verify if NTLM or Kerberos backends are configured: grep -r 'NTLM\|Negotiate\|Kerberos' /etc/traefik/ or check your traefik.yml/toml for auth-forwardauth middleware with these schemes
- Search Traefik access logs for repeated TLS handshake errors or certificate verification failures followed by requests to different backend services on the same connection: grep -E 'TLS|certificate|peer' /var/log/traefik/access.log
- Confirm fix application by verifying version is ≥2.11.58 (v2) or ≥3.7.14 (v3): traefik version and cross-check against the fixed versions in your deployment
FAQ
What is CVE-2026-114642?
This CVE describes a TLS client configuration reuse flaw in Traefik where NTLM/Kerberos authentication credentials cached in a keep-alive connection slot can be replayed to bypass certificate verification when reaching different backend services. An attacker can exploit this to access services with forged or missing certificate validation.
Is CVE-2026-114642 being actively exploited?
No, this vulnerability is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog and no public exploit code is currently available, though the attack requires network access to a Traefik instance configured with NTLM or Kerberos backends.
What versions of Traefik are affected by CVE-2026-114642?
Traefik 2.11.0 through 2.11.57 and 3.0.0 through 3.7.13 are vulnerable. Versions 2.11.58 and 3.7.14 (and later) include the fix.
How do I check if my server is vulnerable to CVE-2026-114642?
Run 'traefik version' and compare the version number against the vulnerable ranges above. If you are running 2.11.x (before 2.11.58) or 3.x (before 3.7.14), your instance is vulnerable if NTLM or Kerberos authentication is enabled on any backend.
Does Defensia detect CVE-2026-114642?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Traefik is installed on a monitored server, CVE-2026-114642 will appear in your dashboard with remediation steps.
Related Traefik CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-114642. Free for 1 server.
Get started free