CVE-2026-53622

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 85% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 10.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Traefik is an HTTP reverse proxy and load balancer. Prior to 3.7.3, there is a critical vulnerability in Traefik's HTTP/3 (QUIC) TLS configuration selection that allows unauthenticated clients to bypass router-specific mTLS enforcement. When HTTP/3 is enabled on an entrypoint, the TLS handshake selects the applicable TLS configuration through an exact, case-sensitive lookup on the SNI value, which fails to match wildcard host patterns (e.g., *.example.com) or case variants of the configured hostname. Because the handshake falls back to the default TLS configuration — which may not require client certificates — a client can complete the QUIC handshake without presenting a certificate, while the subsequent HTTP routing layer still dispatches the request to a backend protected by a router-specific mTLS policy. The issue affects deployments where HTTP/3 is enabled, a router uses a wildcard Host rule or case-insensitive hostname matching, a router-specific TLSOptions enforces client certificate authentication, and UDP access to the entrypoint is reachable by an attacker. This vulnerability is fixed in 3.7.3.

CVSS v3
10.0
EG Score
10.0(medium)
EPSS
15.0%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 30, 2026

Advisory Details (5)

Auto-updated Jun 30, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, redhat.
redhat

2491924 – (CVE-2026-53622) CVE-2026-53622 github.com/traefik/traefik: Traefik: mTLS enforcement bypass due to HTTP/3 TLS configuration flaw

https://bugzilla.redhat.com/show_bug.cgi?id=2491924
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-53622
github Patch Available🟡 PoC Available

HTTP/3 mTLS bypass via exact SNI TLSOptions lookup for wildcard and mixed-case hosts · Advisory · traefik/traefik · GitHub

https://github.com/traefik/traefik/security/advisories/GHSA-9cr8-q42q-g8m7
github_release Patch Available

v3.7.3

Patch available: traefik/traefik v3.7.3

https://github.com/traefik/traefik/releases/tag/v3.7.3

Vendor Advisories for CVE-2026-53622(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/traefik/traefik
github.com/traefik/traefik/v2
Traefik3.7.3

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 45× in last 7d / 80× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 03:01 UTCEG score recompute
  2. 2026-07-06 22:58 UTCEG score recompute
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 05:18 UTCEG score recompute
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 01:11 UTCEG score recompute
  9. 2026-07-05 21:00 UTCEG score recompute
  10. 2026-07-05 16:56 UTCEG score recompute
  11. 2026-07-05 12:45 UTCEG score recompute
  12. 2026-07-05 08:41 UTCEG score recompute
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-05 02:30 UTCEG score recompute
  16. 2026-07-04 22:29 UTCEG score recompute
  17. 2026-07-04 18:29 UTCEG score recompute
  18. 2026-07-04 12:59 UTCEG score recompute
  19. 2026-07-04 08:59 UTCEG score recompute
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 01:54 UTCEG score recompute
  23. 2026-07-03 21:45 UTCEG score recompute
  24. 2026-07-03 17:44 UTCEG score recompute
  25. 2026-07-03 13:44 UTCEG score recompute
Show 55 more
  1. 2026-07-03 07:16 UTCEG score recompute
  2. 2026-07-03 03:15 UTCEG score recompute
  3. 2026-07-02 23:14 UTCEG score recompute
  4. 2026-07-02 19:14 UTCEG score recompute
  5. 2026-07-02 15:13 UTCEG score recompute
  6. 2026-07-02 11:13 UTCEG score recompute
  7. 2026-07-02 06:38 UTCEG score recompute
  8. 2026-07-02 02:39 UTCEG score recompute
  9. 2026-07-01 22:38 UTCEG score recompute
  10. 2026-07-01 18:24 UTCEG score recompute
  11. 2026-07-01 15:07 UTCEPSS rescore
  12. 2026-07-01 14:24 UTCEG score recompute
  13. 2026-07-01 10:24 UTCEG score recompute
  14. 2026-07-01 06:24 UTCEG score recompute
  15. 2026-07-01 02:24 UTCEG score recompute
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 22:24 UTCEG score recompute
  18. 2026-06-30 18:24 UTCEG score recompute
  19. 2026-06-30 14:23 UTCEG score recompute
  20. 2026-06-30 10:12 UTCEG score recompute
  21. 2026-06-30 06:02 UTCEG score recompute
  22. 2026-06-30 02:01 UTCEG score recompute
  23. 2026-06-29 22:00 UTCEG score recompute
  24. 2026-06-29 17:59 UTCEG score recompute
  25. 2026-06-29 14:06 UTCEPSS rescore
  26. 2026-06-29 14:06 UTCEPSS rescore
  27. 2026-06-29 13:58 UTCEG score recompute
  28. 2026-06-29 09:58 UTCEG score recompute
  29. 2026-06-29 05:58 UTCEG score recompute
  30. 2026-06-29 01:53 UTCEG score recompute
  31. 2026-06-28 21:53 UTCEG score recompute
  32. 2026-06-28 17:53 UTCEG score recompute
  33. 2026-06-28 14:07 UTCEPSS rescore
  34. 2026-06-28 13:53 UTCEG score recompute
  35. 2026-06-28 09:52 UTCEG score recompute
  36. 2026-06-28 05:52 UTCEG score recompute
  37. 2026-06-28 04:56 UTCEPSS rescore
  38. 2026-06-28 04:56 UTCEPSS rescore
  39. 2026-06-28 01:37 UTCEG score recompute
  40. 2026-06-27 21:35 UTCEG score recompute
  41. 2026-06-27 17:35 UTCEG score recompute
  42. 2026-06-27 13:34 UTCEG score recompute
  43. 2026-06-27 09:34 UTCEG score recompute
  44. 2026-06-27 05:33 UTCEG score recompute 2.20
  45. 2026-06-27 03:08 UTCEPSS rescore
  46. 2026-06-26 17:41 UTCNVD updateCVSS v3 → 10 · severity → CRITICAL
  47. 2026-06-26 16:27 UTCEG score recompute
  48. 2026-06-26 03:22 UTCEG score recompute
  49. 2026-06-25 14:15 UTCEG score recompute
  50. 2026-06-25 13:49 UTCEPSS rescore
  51. 2026-06-25 01:09 UTCEG score recompute
  52. 2026-06-24 14:05 UTCEPSS rescore
  53. 2026-06-24 12:03 UTCEG score recompute 7.80
  54. 2026-06-24 12:01 UTCNVD updateCVSS v3 → 7.8 · CVSS v4 → 7.8
  55. 2026-06-16 21:06 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-53622?
CVE-2026-53622 is a critical vulnerability published on June 16, 2026. Traefik is an HTTP reverse proxy and load balancer. Prior to 3.7.3, there is a critical vulnerability in Traefik's HTTP/3 (QUIC) TLS configuration selection that allows unauthenticated clients to bypass router-specific mTLS enforcement. When HTTP/3 is enabled on an entrypoint, the TLS handshake…
When was CVE-2026-53622 disclosed?
CVE-2026-53622 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53622 actively exploited?
CVE-2026-53622 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53622?
CVE-2026-53622 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-53622?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53622, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53622

Explore →

Is Your Infrastructure Affected by CVE-2026-53622?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.