CVE-2026-114635·Traefik vulnerability
Traefik before v2.11.58 and v3.7.14 contains an authentication bypass vulnerability in its SNI check, which is skipped when request TLS state is nil. Unauthenticated clients can send HTTP/2 requests with the :scheme http pseudo-header over TLS on Go 1.27 builds to reach routers requiring client certificates without presenting one.
- 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 to version 3.7.14 or later to patch the SNI validation bypass that allows unauthenticated clients to bypass client certificate requirements. Organizations running versions 3.0.0 through 3.7.14 should prioritize this update, particularly if their infrastructure relies on mutual TLS authentication for access control. After upgrading, verify that SNI checks are properly enforced on all TLS connections.
sudo dnf update traefikDefensia detects this vulnerability
What an exploitation attempt looks like
Sample log line indicative of exploitation attempts:
HTTP/2 requests with ':scheme http' pseudo-header received over TLS connections to port 443 or custom HTTPS entry points, combined with missing or invalid client certificate chains, followed by successful routing to protected backendsWAF mitigation (if patching is not yet possible)
Add this rule to your WAF to block exploitation attempts while you schedule the patch.
Implement WAF rules to enforce strict HTTP/2 scheme validation: block any HTTP/2 requests with ':scheme http' arriving on HTTPS-only entry points; monitor and alert on protocol mismatches between the transport layer (TLS) and application-layer scheme declarationsHow to check if you are affected
- Check installed version: traefik version | grep -oP 'Version=\K[^,]+' or docker inspect $(docker ps -q --filter 'ancestor=traefik:latest') | grep -i version
- Verify TLS entry points are configured: grep -A 10 'entryPoints' /etc/traefik/traefik.yml | grep -E '(tls|clientAuth)' to confirm client certificate requirements are set
- Search logs for HTTP/2 requests with :scheme pseudo-header mismatches: grep -i ':scheme http' /var/log/traefik/access.log | grep -v 'status.*[23][0-9][0-9]' to identify anomalous patterns
- Confirm the fix: traefik version | grep -E '(3\.7\.14|3\.[8-9]|[4-9]\.)' to ensure patched version is running
FAQ
What is CVE-2026-114635?
This vulnerability is an SNI (Server Name Indication) check bypass in Traefik that allows attackers to send specially crafted HTTP/2 requests over TLS without presenting required client certificates, effectively circumventing mutual TLS authentication policies that protect sensitive backends.
Is CVE-2026-114635 being actively exploited?
No, this vulnerability is not currently listed on CISA's KEV (Known Exploited Vulnerabilities) catalog, and no public exploit code has been released. However, the attack method is straightforward for skilled threat actors targeting environments with strict mTLS policies.
What versions of Traefik are affected by CVE-2026-114635?
Traefik versions 3.0.0 through 3.7.13 are vulnerable. Version 2.11.57 and earlier in the v2 branch are also affected. The fix is available in v3.7.14 and later, and v2.11.58 and later.
How do I check if my server is vulnerable to CVE-2026-114635?
Run 'traefik version' and compare the reported version against the vulnerable ranges (3.0.0–3.7.13 or 2.0.0–2.11.57). If your version falls within these ranges and you have TLS entry points configured with client authentication, your deployment is vulnerable.
Does Defensia detect CVE-2026-114635?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Traefik is installed on a monitored server, CVE-2026-114635 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-114635. Free for 1 server.
Get started free