CVE-2026-39858

CRITICALNVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 69% 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
Trending — 3 sources updated this week
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

A fix is available — apply it.

Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is a high severity authentication bypass vulnerability in Traefik's ForwardAuth and snippet-based authentication middleware. Traefik's forwarded-header sanitization logic targets only canonical header names (e.g., X-Forwarded-Proto) and does not strip or normalize alias variants that use underscores instead of dashes (e.g., X_Forwarded_Proto). These unsanitized alias headers are forwarded intact to the authentication backend. When the backend normalizes underscore and dash header forms equivalently, an attacker can inject spoofed trust context — such as a trusted scheme or host — through the alias headers and bypass authentication on protected routes without valid credentials. This issue has been patched in versions 2.11.43, 3.6.14, and 3.7.0-rc.2.

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

Published

April 30, 2026

Last Modified

July 15, 2026

Advisory Details (8)

Auto-updated Jul 15, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, redhat.
redhat Patch Available
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-39858.json
redhat

2464234 – (CVE-2026-39858) CVE-2026-39858 traefik: Traefik: Authentication bypass via unsanitized alias headers

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-39858
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:21772
github Patch Available🟡 PoC Available

Forwarded alias spoofing top pre-auth decision bypass · Advisory · traefik/traefik · GitHub

https://github.com/traefik/traefik/security/advisories/GHSA-5m6w-wvh7-57vm
github_release Patch Available

v3.7.0-rc.2

Patch available: traefik/traefik v3.7.0-rc.2 (pre-release)

https://github.com/traefik/traefik/releases/tag/v3.7.0-rc.2
github_release Patch Available

v3.6.14

Patch available: traefik/traefik v3.6.14

https://github.com/traefik/traefik/releases/tag/v3.6.14
github_release Patch Available

v2.11.43

Patch available: traefik/traefik v2.11.43

https://github.com/traefik/traefik/releases/tag/v2.11.43

Vendor Advisories for CVE-2026-39858(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatdevspaces/traefik-rhel9:17797867792026-05-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/traefik/traefik———
github.com/traefik/traefik/v2—2.11.43—
github.com/traefik/traefik/v3—3.6.14—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 37× 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.

Showing the most recent 100 of 240 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:25 UTCNVD updateCVSS v3 → 10 · severity → CRITICAL
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 01:21 UTCMITRE cvelistV5CVSS v3 → 8.2 · severity → HIGH
  6. 2026-07-13 22:30 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-08 15:15 UTCEPSS rescore
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 13:49 UTCEPSS rescore
Show 75 more
  1. 2026-06-24 14:05 UTCEPSS rescore
  2. 2026-06-23 21:33 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-22 14:25 UTCEPSS rescore
  5. 2026-06-21 14:56 UTCEPSS rescore
  6. 2026-06-21 14:56 UTCEPSS rescore
  7. 2026-06-21 01:59 UTCEPSS rescore
  8. 2026-06-19 19:25 UTCEPSS rescore
  9. 2026-06-18 17:52 UTCEPSS rescore
  10. 2026-06-18 17:52 UTCEPSS rescore
  11. 2026-06-17 17:53 UTCEPSS rescore
  12. 2026-06-16 17:52 UTCEPSS rescore
  13. 2026-06-15 17:49 UTCEPSS rescore
  14. 2026-06-15 03:59 UTCEG score recompute
  15. 2026-06-15 03:59 UTCVendor advisory
  16. 2026-06-15 00:15 UTCEG score recompute
  17. 2026-06-15 00:15 UTCVendor advisory
  18. 2026-06-14 23:18 UTCEPSS rescore
  19. 2026-06-14 20:13 UTCEG score recompute
  20. 2026-06-14 20:13 UTCVendor advisory
  21. 2026-06-14 16:26 UTCEG score recompute
  22. 2026-06-14 16:26 UTCVendor advisory
  23. 2026-06-14 09:15 UTCEG score recompute
  24. 2026-06-14 09:15 UTCVendor advisory
  25. 2026-06-13 23:00 UTCEPSS rescore
  26. 2026-06-12 23:12 UTCEPSS rescore
  27. 2026-06-12 23:12 UTCEPSS rescore
  28. 2026-06-12 11:56 UTCEG score recompute
  29. 2026-06-12 11:56 UTCVendor advisory
  30. 2026-06-12 08:14 UTCEG score recompute
  31. 2026-06-12 08:14 UTCVendor advisory
  32. 2026-06-12 04:32 UTCEG score recompute
  33. 2026-06-12 04:32 UTCVendor advisory
  34. 2026-06-12 00:51 UTCEG score recompute
  35. 2026-06-12 00:51 UTCVendor advisory
  36. 2026-06-11 21:08 UTCEG score recompute
  37. 2026-06-11 21:08 UTCVendor advisory
  38. 2026-06-11 17:27 UTCEG score recompute
  39. 2026-06-11 17:27 UTCVendor advisory
  40. 2026-06-11 14:00 UTCEPSS rescore
  41. 2026-06-11 13:21 UTCEG score recompute
  42. 2026-06-11 13:21 UTCVendor advisory
  43. 2026-06-11 09:32 UTCEG score recompute
  44. 2026-06-11 09:32 UTCVendor advisory
  45. 2026-06-11 04:47 UTCEG score recompute
  46. 2026-06-11 04:47 UTCVendor advisory
  47. 2026-06-10 22:54 UTCEG score recompute
  48. 2026-06-10 22:54 UTCVendor advisory
  49. 2026-06-10 22:18 UTCEPSS rescore
  50. 2026-06-10 19:11 UTCEG score recompute
  51. 2026-06-10 19:11 UTCVendor advisory
  52. 2026-06-10 15:29 UTCEG score recompute
  53. 2026-06-10 15:29 UTCVendor advisory
  54. 2026-06-10 13:22 UTCEPSS rescore
  55. 2026-06-10 11:47 UTCEG score recompute
  56. 2026-06-10 11:47 UTCVendor advisory
  57. 2026-06-10 08:06 UTCEG score recompute
  58. 2026-06-10 08:06 UTCVendor advisory
  59. 2026-06-10 03:10 UTCEG score recompute
  60. 2026-06-10 03:10 UTCVendor advisory
  61. 2026-06-09 23:28 UTCEG score recompute
  62. 2026-06-09 23:28 UTCVendor advisory
  63. 2026-06-09 18:09 UTCEG score recompute
  64. 2026-06-09 18:09 UTCVendor advisory
  65. 2026-06-09 14:27 UTCEG score recompute
  66. 2026-06-09 14:27 UTCVendor advisory
  67. 2026-06-09 10:45 UTCEG score recompute
  68. 2026-06-09 10:45 UTCVendor advisory
  69. 2026-06-09 07:04 UTCEG score recompute
  70. 2026-06-09 07:04 UTCVendor advisory
  71. 2026-06-09 03:22 UTCEG score recompute
  72. 2026-06-09 03:22 UTCVendor advisory
  73. 2026-06-08 23:39 UTCEG score recompute
  74. 2026-06-08 23:39 UTCVendor advisory
  75. 2026-06-08 14:17 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-39858?
CVE-2026-39858 is a critical vulnerability published on April 30, 2026. Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is a high severity authentication bypass vulnerability in Traefik's ForwardAuth and snippet-based authentication middleware. Traefik's forwarded-header sanitization logic targets only…
When was CVE-2026-39858 disclosed?
CVE-2026-39858 was first published in the National Vulnerability Database on April 30, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-39858 actively exploited?
CVE-2026-39858 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 38.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-39858?
CVE-2026-39858 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-39858?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39858, 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-39858

Explore →

Is Your Infrastructure Affected by CVE-2026-39858?

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

Start Free Scan →Browse All CVEs