CVE-2026-7307

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-19. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in Keycloak. A remote, unauthenticated attacker can send a specially crafted XML input to the Security Assertion Markup Language (SAML) endpoint. This malicious input can cause high CPU usage and worker thread starvation, leading to a Denial of Service (DoS) where the server becomes unavailable.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.0%
EPSS %ILE
62nd
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

May 19, 2026

Last Modified

October 6, 2026

Advisory Details (6)

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

2476526 – (CVE-2026-7307) CVE-2026-7307 keycloak: Keycloak: Denial of Service via specially crafted SAML input

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-7307
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19597
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19596
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19595
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19594

Vendor Advisories for CVE-2026-7307(10)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrh-sso7-keycloak-0:18.0.20-1.redhat_00001.1.el8sso2026-10-06redhat
redhatrh-sso-7/sso76-openshift-rhel8:7.6-852026-10-05redhat
redhatkeycloak-services2026-10-05redhat
redhatrhbk/keycloak-rhel92026-05-20redhat
redhatrhbk/keycloak-rhel9-operator:26.2-212026-05-20redhat
redhatrhbk/keycloak-rhel9-operator:26.4-172026-05-20redhat

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-saml-core1.1.0.Beta1 ... 9.0.3 (207 versions)
  • every version up to 26.6.2: fixed in 26.6.2
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

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

Frequently asked(5)

What is CVE-2026-7307?
CVE-2026-7307 is a high vulnerability published on May 19, 2026. A flaw was found in Keycloak. A remote, unauthenticated attacker can send a specially crafted XML input to the Security Assertion Markup Language (SAML) endpoint. This malicious input can cause high CPU usage and worker thread starvation, leading to a Denial of Service (DoS) where the server…
When was CVE-2026-7307 disclosed?
CVE-2026-7307 was first published on May 19, 2026, with the most recent update on October 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7307 actively exploited?
CVE-2026-7307 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-7307?
CVE-2026-7307 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-7307?
A fix for CVE-2026-7307 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-7307 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-2026-7307

Explore →

Is Your Infrastructure Affected by CVE-2026-7307?

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

Book a Demo →Browse All CVEs