CVE-2026-46579

HIGHNVD 7.57.4▼
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-05-29. NVD baseline CVSS 7.5; sources differ by 0.1.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — Patch released this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

A flaw was found in the OpenShift Router. When a Route has insecureEdgeTerminationPolicy set to Allow, the HTTP frontend does not remove X-SSL-Client-* headers from incoming requests. This allows an unauthenticated attacker to send plain HTTP requests with crafted X-SSL-Client-* headers. As a result, backends relying on these headers for mutual TLS (Transport Layer Security) authentication can be bypassed, enabling the attacker to impersonate client certificate identities.

CVSS v3
7.5
EG Score
7.4(medium)
EPSS
14.8%
KEV
Not listed

Published

May 29, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated Jun 6, 2026
Patch available. Sources: redhat.
redhat

2483181 – (CVE-2026-46579) CVE-2026-46579 openshift/router: openshift/router: mTLS client certificate spoofing via unstripped X-SSL-Client headers on HTTP frontend

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-46579

Vendor Advisories for CVE-2026-46579(5)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift4/ose-haproxy-router-rhel9:17834456422026-07-15redhat
redhatopenshift4/ose-haproxy-router-rhel9:17816390272026-06-23redhat
redhatopenshift4/ose-haproxy-router-rhel9:17815521702026-06-23redhat
redhatopenshift4/ose-haproxy-router-rhel9:17816439672026-06-23redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 106× 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 195 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-46579?
CVE-2026-46579 is a high vulnerability published on May 29, 2026. A flaw was found in the OpenShift Router. When a Route has insecureEdgeTerminationPolicy set to Allow, the HTTP frontend does not remove X-SSL-Client- headers from incoming requests. This allows an unauthenticated attacker to send plain HTTP requests with crafted X-SSL-Client- headers. As a result,…
When was CVE-2026-46579 disclosed?
CVE-2026-46579 was first published in the National Vulnerability Database on May 29, 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-46579 actively exploited?
CVE-2026-46579 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46579?
CVE-2026-46579 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.4.
How do I remediate CVE-2026-46579?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46579, 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

Explore the affected products and dependency analysis for CVE-2026-46579

Explore →

Is Your Infrastructure Affected by CVE-2026-46579?

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

Start Free Scan →Browse All CVEs