CVE-2025-3501

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 62% 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
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in Keycloak. By setting a verification policy to 'ALL', the trust store certificate verification is skipped, which is unintended.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
52
EG Risk 52/100

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
Severity82% × 45%
Exploitation0% × 40%
Automatability100% × 15%
EPSS PROB
0.5%
EPSS %ILE
37th
KEV
Not listed

Published

April 29, 2025

Last Modified

September 21, 2026

Advisory Details (8)

Auto-updated Sep 8, 2026
Patch available. Sources: github_pr, redhat.
github_pr

fix: remove ANY mode modification of truststores

Fix merged in keycloak/keycloak PR #39366 on 2025-04-30 — awaiting tagged release

https://github.com/keycloak/keycloak/pull/39366
generic

CVE-2025-3501 Keycloak hostname verification · Issue #39350 · keycloak/keycloak · GitHub

https://github.com/keycloak/keycloak/issues/39350
redhatMentions a patch (unverified)

2358834 – (CVE-2025-3501) CVE-2025-3501 org.keycloak.protocol.services: Keycloak hostname verification

https://bugzilla.redhat.com/show_bug.cgi?id=2358834
redhatMentions a patch (unverified)

CVE-2025-3501 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2025-3501
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:8690
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:8672
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:4336
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:4335

Vendor Advisories for CVE-2025-3501(4)

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 / EcosystemFix (by version range) / PatchReleasedSource
redhatpatch2025-06-09redhat
redhatrhbk/keycloak-rhel9-operator:26.2-42025-06-09redhat
redhatkeycloak2025-04-29redhat
redhatrhbk/keycloak-rhel9-operator:26.0-132025-04-29redhat

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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.keycloak:keycloak-services1.0-alpha-1 ... 9.0.3 (198 versions)
  • every version up to 26.2.2: fixed in 26.2.2
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same vendor + same CWE)

Same vendor

3 shown

redhat:RHSA-2025:8672 · redhat:RHSA-2025:4335

Frequently asked(5)

What is CVE-2025-3501?
CVE-2025-3501 is a high vulnerability published on April 29, 2025. A flaw was found in Keycloak. By setting a verification policy to 'ALL', the trust store certificate verification is skipped, which is unintended.
When was CVE-2025-3501 disclosed?
CVE-2025-3501 was first published on April 29, 2025, with the most recent update on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-3501 actively exploited?
CVE-2025-3501 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-3501?
CVE-2025-3501 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2025-3501?
A fix for CVE-2025-3501 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-3501 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-3501

Explore →

Is Your Infrastructure Affected by CVE-2025-3501?

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

Book a Demo →Browse All CVEs