CVE-2026-9800

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH 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.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 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(high)
EPSS
21.8%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 2, 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 43× in last 7d / 73× 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.

  1. 2026-07-06 18:15 UTCEG score recompute
  2. 2026-07-06 18:15 UTCVendor advisory
  3. 2026-07-06 18:15 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 05:14 UTCEG score recompute
  6. 2026-07-06 05:14 UTCVendor advisory
  7. 2026-07-06 05:13 UTCGHSA enrichment
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 16:12 UTCEG score recompute
  10. 2026-07-05 16:12 UTCVendor advisory
  11. 2026-07-05 16:12 UTCGHSA enrichment
  12. 2026-07-05 03:11 UTCEG score recompute
  13. 2026-07-05 03:11 UTCVendor advisory
  14. 2026-07-05 03:11 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-04 14:12 UTCEG score recompute
  17. 2026-07-04 14:12 UTCVendor advisory
  18. 2026-07-04 14:12 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 01:12 UTCEG score recompute
  21. 2026-07-04 01:12 UTCVendor advisory
  22. 2026-07-04 01:12 UTCGHSA enrichment
  23. 2026-07-03 12:12 UTCEG score recompute
  24. 2026-07-03 12:12 UTCVendor advisory
  25. 2026-07-03 12:11 UTCGHSA enrichment
Show 48 more
  1. 2026-07-02 22:58 UTCEG score recompute
  2. 2026-07-02 22:58 UTCVendor advisory
  3. 2026-07-02 22:58 UTCGHSA enrichment
  4. 2026-07-02 17:02 UTCEPSS rescore
  5. 2026-07-02 09:59 UTCEG score recompute
  6. 2026-07-02 09:59 UTCVendor advisory
  7. 2026-07-02 09:58 UTCGHSA enrichment
  8. 2026-07-01 20:59 UTCEG score recompute
  9. 2026-07-01 20:59 UTCVendor advisory
  10. 2026-07-01 20:59 UTCGHSA enrichment
  11. 2026-07-01 15:07 UTCEPSS rescore
  12. 2026-07-01 08:00 UTCEG score recompute
  13. 2026-07-01 08:00 UTCVendor advisory
  14. 2026-07-01 08:00 UTCGHSA enrichment
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-30 19:00 UTCEG score recompute
  17. 2026-06-30 19:00 UTCVendor advisory
  18. 2026-06-30 19:00 UTCGHSA enrichment
  19. 2026-06-30 06:00 UTCEG score recompute
  20. 2026-06-30 06:00 UTCVendor advisory
  21. 2026-06-30 06:00 UTCGHSA enrichment
  22. 2026-06-29 17:01 UTCEG score recompute
  23. 2026-06-29 17:01 UTCVendor advisory
  24. 2026-06-29 17:00 UTCGHSA enrichment
  25. 2026-06-29 14:06 UTCEPSS rescore
  26. 2026-06-29 04:00 UTCEG score recompute
  27. 2026-06-29 04:00 UTCVendor advisory
  28. 2026-06-29 04:00 UTCGHSA enrichment
  29. 2026-06-28 14:55 UTCEG score recompute
  30. 2026-06-28 14:55 UTCVendor advisory
  31. 2026-06-28 14:55 UTCGHSA enrichment
  32. 2026-06-28 14:07 UTCEPSS rescore
  33. 2026-06-28 04:56 UTCEPSS rescore
  34. 2026-06-28 01:56 UTCEG score recompute
  35. 2026-06-28 01:56 UTCVendor advisory
  36. 2026-06-28 01:56 UTCGHSA enrichment
  37. 2026-06-27 12:56 UTCEG score recompute
  38. 2026-06-27 12:56 UTCVendor advisory
  39. 2026-06-27 12:56 UTCGHSA enrichment
  40. 2026-06-27 03:08 UTCEPSS rescore
  41. 2026-06-26 23:56 UTCEG score recompute
  42. 2026-06-26 23:56 UTCVendor advisory
  43. 2026-06-26 23:56 UTCGHSA enrichment
  44. 2026-06-26 10:57 UTCEG score recompute
  45. 2026-06-26 10:57 UTCVendor advisory
  46. 2026-06-26 10:57 UTCGHSA enrichment
  47. 2026-06-25 17:50 UTCEG score recompute
  48. 2026-06-25 17:48 UTCNVD updatefirst tracked

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 2, 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 21.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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