traefik · Traefik · published 2026-06-23

CVE-2026-48491Traefik: SNICheck ignores wildcard TLSOptions mappings, allowing domain-fronted mTLS bypass

Routine No exploitation evidence; EPSS 0.4%.

CVE-2026-48491 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 30% of all CVEs. This Traefik vulnerability: CVSS 7.8 (v4.0), attacks can be automated, a successful attack gives total control of the component. Fixed upstream in Traefik 3.7.3, 3.6.19, 2.11.48. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Traefik 3.7.3, 3.6.19, 2.11.48.

Patch events

  1. This monthSecurity release

    Web serverTraefik

    Traefik security releases: 3.7.3, 3.6.19, 2.11.48

    Upgrade to 3.7.33.6.192.11.48

    Why: Vendor security release for server software (most severe: CVE-2026-48020).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (30th pct)FIRST EPSS v2026.06.15
CVSS base score7.8 (v4.0)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Traefik is an HTTP reverse proxy and load balancer. From 3.7.0 until 3.7.3, there is a high severity vulnerability in Traefik's domain-fronting protection (SNICheck) that allows an unauthenticated client to bypass mutual TLS enforced through wildcard router TLSOptions. When a router uses a wildcard host rule such as Host(*.example.com) with stricter TLS options (for example RequireAndVerifyClientCert), SNICheck resolves the TLS options for the HTTP Host header using exact map lookups only and never applies wildcard matching. If another permissive SNI is served on the same entrypoint, an attacker can complete the TLS handshake under the permissive options and then send an HTTP Host header targeting the wildcard-protected backend, reaching it without presenting a client certificate. This affects the regular HTTPS / HTTP-2 path and does not require HTTP/3. This vulnerability is fixed in 3.7.3.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →