CVE-2026-57817

CRITICALPre-NVD 8.19.8▲
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.1; sources differ by 1.7.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The OpenID Connect Core 1.0 specification mandates that the RP MUST validate the c_hash parameter when operating in the Hybrid Flow. If an Apache CXF RP is integrated with a non-compliant or misconfigured Identity Provider (IdP) that omits the c_hash, the RP becomes vulnerable to Authorization Code Substitution/Injection attacks. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue.

CVSS v3
8.1
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 6, 2026

Last Modified

August 7, 2026

Advisory Details (1)

Auto-updated Aug 6, 2026
Patch available.
generic
https://lists.apache.org/thread/pj63c3pf7kkp1xhr53do704fwj3t3htn

Vendor Advisories for CVE-2026-57817(2)

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 / EcosystemFix (by version range) / PatchReleasedSource
redhatcxf2026-09-24redhat

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 36× in last 7d / 162× 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 385 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-57817?
CVE-2026-57817 is a critical vulnerability published on August 6, 2026. The OpenID Connect Core 1.0 specification mandates that the RP MUST validate the chash parameter when operating in the Hybrid Flow. If an Apache CXF RP is integrated with a non-compliant or misconfigured Identity Provider (IdP) that omits the chash, the RP becomes vulnerable to Authorization Code…
When was CVE-2026-57817 disclosed?
CVE-2026-57817 was first published on August 6, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57817 actively exploited?
CVE-2026-57817 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57817?
CVE-2026-57817 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2026-57817?
A fix for CVE-2026-57817 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57817 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-57817?

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

Book a Demo →Browse All CVEs