CVE-2026-9087

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in Keycloak. The cross-session verification proof is keyed only by (local userId, idpAlias) and is not bound to the upstream identity that was actually verified, so a second upstream account on the same IdP can consume it and get linked to the victim's local account.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

Published

May 20, 2026

Last Modified

August 3, 2026

Advisory Details (2)

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

2480172 – (CVE-2026-9087) CVE-2026-9087 keycloak: Cross-Session Email Verification Proof Not Bound to Upstream Identity in First-Broker-Login

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

cve-details

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

Vendor Advisories for CVE-2026-9087(5)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhbk/keycloak-rhel92026-06-25redhat
redhatrhbk/keycloak-rhel9-operator:26.4-192026-06-25redhat
redhatrhbk/keycloak-rhel9-operator:26.6-62026-06-10redhat

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 (227 versions)
  • every version up to 26.6.3: fixed in 26.6.3
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

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

Frequently asked(5)

What is CVE-2026-9087?
CVE-2026-9087 is a high vulnerability published on May 20, 2026. A flaw was found in Keycloak. The cross-session verification proof is keyed only by (local userId, idpAlias) and is not bound to the upstream identity that was actually verified, so a second upstream account on the same IdP can consume it and get linked to the victim's local account.
When was CVE-2026-9087 disclosed?
CVE-2026-9087 was first published on May 20, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9087 actively exploited?
CVE-2026-9087 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9087?
CVE-2026-9087 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-9087?
A fix for CVE-2026-9087 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-9087 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-9087

Explore →

Is Your Infrastructure Affected by CVE-2026-9087?

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

Book a Demo →Browse All CVEs