Security readout for executives and security teams
Plain-English summary
Traefik can be tricked into treating some TLS connections as if they did not name a protected service. In affected versions, that can route traffic through a default TLS setup that usually does not require client certificates, bypassing mTLS controls intended to protect backend services.
Executive priority
Treat as high priority where Traefik enforces mTLS for sensitive services. This can undermine a core access-control boundary without credentials. Patch exposed or security-critical gateways first, then validate configuration so default TLS behavior cannot weaken intended mTLS protections.
Technical view
The issue is in Traefik TLS SNI pre-sniffing for fragmented ClientHello records. SNI extraction may fail with EOF and return an empty SNI, causing the TCP router to use the default TLS configuration instead of route-level mTLS requirements. CVSS is 8.3 high with network, unauthenticated attack characteristics.
Likely exposure
Exposure is most likely where Traefik handles TCP/TLS routes that rely on route-level mTLS enforcement. Affected ranges include Traefik < 2.11.41, >= 3.0.0-beta1 and < 3.6.11, and >= 3.7.0-ea.1 and < 3.7.0-ea.2.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. The weakness is remotely reachable, unauthenticated, and low complexity according to CVSS, but exploitation status should not be assumed beyond the provided sources.
Researcher notes
The key control-flow issue is SNI extraction failure on fragmented ClientHello records leading to empty SNI and default TLS config selection. The source bundle contains a minor version wording inconsistency, but its structured affected data and patch list identify fixed versions.
Mitigation direction
- Upgrade Traefik to 2.11.41, 3.6.11, or 3.7.0-ea.2 as applicable.
- Review vendor advisories for Red Hat-packaged Traefik exposure and errata applicability.
- Check whether default TLS configurations require client certificates where mTLS is expected.
- Prioritize internet-facing Traefik instances and routes protecting sensitive internal services.
- Monitor Traefik and access logs for unexpected access to mTLS-protected services.
Validation and detection
- Inventory Traefik versions across container images, hosts, and bundled platform packages.
- Identify TCP/TLS routers that rely on client certificate authentication.
- Confirm upgraded instances report a fixed version from the vendor-supported release line.
- Validate that protected routes reject clients without valid certificates.
- Review default TLS configuration for unintended non-mTLS fallback behavior.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1188: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-179: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-32305 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L3.93.7redhat-SADPCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
7.8HighVector: 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
Base CVSS 3.1 score
8.3HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-03-20T11:02:42.394Z: Reported to Red Hat.
- 2026-03-20T10:01:13.620Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/traefik/traefik/security/advisories/GHSA-wvvq-wgcr-9q48CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/traefik/traefik/releases/tag/v2.11.41CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/traefik/traefik/releases/tag/v3.6.11CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/traefik/traefik/releases/tag/v3.7.0-ea.2CVE reference, GitHub_M · x_refsource_MISC
- https://access.redhat.com/security/cve/CVE-2026-32305CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2449595CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-32305.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:10175CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:21772CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Initialization of a Resource with an Insecure Default
Initialization of a Resource with an Insecure Default represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Behavior Order: Early Validation
Incorrect Behavior Order: Early Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.