CVE-2026-9800

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
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%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in Keycloak Policy Enforcer. This vulnerability allows any authenticated user to bypass all authorization policies, including role, scope, and User-Managed Access (UMA) permission checks. By including the configured access-denied page path within a request URL, either as a path segment or a query parameter, an attacker can gain unauthorized access to protected resources.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 15, 2026

Advisory Details (2)

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

2482472 – (CVE-2026-9800) CVE-2026-9800 keycloak: Keycloak Policy Enforcer: Authorization bypass via incorrect URI comparison

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

cve-details

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

Vendor Advisories for CVE-2026-9800(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 / EcosystemFixed in / PatchReleasedSource
redhatrhbk/keycloak-rhel9-operator:26.6-82026-06-25redhat
redhatrhbk/keycloak-rhel92026-06-25redhat
redhatrhbk/keycloak-rhel9-operator:26.4-192026-06-25redhat

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 13× in last 7d / 110× 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 117 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-9800?
CVE-2026-9800 is a high vulnerability published on June 25, 2026. A flaw was found in Keycloak Policy Enforcer. This vulnerability allows any authenticated user to bypass all authorization policies, including role, scope, and User-Managed Access (UMA) permission checks. By including the configured access-denied page path within a request URL, either as a path…
When was CVE-2026-9800 disclosed?
CVE-2026-9800 was first published in the National Vulnerability Database on June 25, 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-9800 actively exploited?
CVE-2026-9800 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.0% of all scored CVEs.
What is the CVSS score of CVE-2026-9800?
CVE-2026-9800 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-9800?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9800, 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-9800

Explore →

Is Your Infrastructure Affected by CVE-2026-9800?

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

Start Free Scan →Browse All CVEs