CVE-2026-11800

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. 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. This JWT algorithm confusion vulnerability in the JWT Authorization Grant flow allows an attacker with valid client credentials to bypass signature verification. By forging an assertion, the attacker can create unauthorized access tokens. This enables the attacker to impersonate any federated user linked to the affected Identity Provider, leading to unauthorized access and potential privilege escalation.

CVSS v3
8.1
EG Score
8.1(high)
EPSS
7.8%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 1, 2026

Advisory Details (4)

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

2487006 – (CVE-2026-11800) CVE-2026-11800 org.keycloak:keycloak-services: Keycloak: Authentication bypass via JWT algorithm confusion

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-11800
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:30084
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:30083

Vendor Advisories for CVE-2026-11800(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2026-06-25redhat
redhatrhbk/keycloak-rhel9-operator:26.6-82026-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 49× in last 7d / 80× 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 20:04 UTCEG score recompute
  2. 2026-07-06 20:04 UTCVendor advisory
  3. 2026-07-06 20:03 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 08:12 UTCEG score recompute
  6. 2026-07-06 08:12 UTCVendor advisory
  7. 2026-07-06 08:12 UTCGHSA enrichment
  8. 2026-07-05 20:22 UTCEG score recompute
  9. 2026-07-05 20:22 UTCVendor advisory
  10. 2026-07-05 20:22 UTCGHSA enrichment
  11. 2026-07-05 08:32 UTCEG score recompute
  12. 2026-07-05 08:32 UTCVendor advisory
  13. 2026-07-05 08:32 UTCGHSA enrichment
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-04 20:43 UTCEG score recompute
  17. 2026-07-04 20:43 UTCVendor advisory
  18. 2026-07-04 20:43 UTCGHSA enrichment
  19. 2026-07-04 08:53 UTCEG score recompute
  20. 2026-07-04 08:53 UTCVendor advisory
  21. 2026-07-04 08:53 UTCGHSA enrichment
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-03 21:04 UTCEG score recompute
  24. 2026-07-03 21:04 UTCVendor advisory
  25. 2026-07-03 21:04 UTCGHSA enrichment
Show 55 more
  1. 2026-07-03 09:14 UTCEG score recompute
  2. 2026-07-03 09:14 UTCVendor advisory
  3. 2026-07-03 09:14 UTCGHSA enrichment
  4. 2026-07-02 21:25 UTCEG score recompute
  5. 2026-07-02 21:25 UTCVendor advisory
  6. 2026-07-02 21:25 UTCGHSA enrichment
  7. 2026-07-02 09:36 UTCEG score recompute
  8. 2026-07-02 09:36 UTCVendor advisory
  9. 2026-07-02 09:36 UTCGHSA enrichment
  10. 2026-07-01 21:47 UTCEG score recompute
  11. 2026-07-01 21:47 UTCVendor advisory
  12. 2026-07-01 21:47 UTCGHSA enrichment
  13. 2026-07-01 15:06 UTCEPSS rescore
  14. 2026-07-01 15:06 UTCEPSS rescore
  15. 2026-07-01 09:58 UTCEG score recompute
  16. 2026-07-01 09:58 UTCVendor advisory
  17. 2026-07-01 09:58 UTCGHSA enrichment
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 22:08 UTCEG score recompute
  20. 2026-06-30 22:08 UTCVendor advisory
  21. 2026-06-30 22:08 UTCGHSA enrichment
  22. 2026-06-30 10:19 UTCEG score recompute
  23. 2026-06-30 10:19 UTCVendor advisory
  24. 2026-06-30 10:18 UTCGHSA enrichment
  25. 2026-06-29 22:28 UTCEG score recompute
  26. 2026-06-29 22:28 UTCVendor advisory
  27. 2026-06-29 22:28 UTCGHSA enrichment
  28. 2026-06-29 14:06 UTCEPSS rescore
  29. 2026-06-29 10:39 UTCEG score recompute
  30. 2026-06-29 10:39 UTCVendor advisory
  31. 2026-06-29 10:39 UTCGHSA enrichment
  32. 2026-06-28 22:49 UTCEG score recompute
  33. 2026-06-28 22:49 UTCVendor advisory
  34. 2026-06-28 22:49 UTCGHSA enrichment
  35. 2026-06-28 14:07 UTCEPSS rescore
  36. 2026-06-28 10:59 UTCEG score recompute
  37. 2026-06-28 10:59 UTCVendor advisory
  38. 2026-06-28 10:59 UTCGHSA enrichment
  39. 2026-06-28 04:56 UTCEPSS rescore
  40. 2026-06-28 04:56 UTCEPSS rescore
  41. 2026-06-27 23:10 UTCEG score recompute
  42. 2026-06-27 23:10 UTCVendor advisory
  43. 2026-06-27 23:09 UTCGHSA enrichment
  44. 2026-06-27 11:19 UTCEG score recompute
  45. 2026-06-27 11:19 UTCVendor advisory
  46. 2026-06-27 11:19 UTCGHSA enrichment
  47. 2026-06-27 03:08 UTCEPSS rescore
  48. 2026-06-26 23:30 UTCEG score recompute
  49. 2026-06-26 23:30 UTCVendor advisory
  50. 2026-06-26 23:30 UTCGHSA enrichment
  51. 2026-06-26 11:41 UTCEG score recompute
  52. 2026-06-26 11:41 UTCVendor advisory
  53. 2026-06-26 11:41 UTCGHSA enrichment
  54. 2026-06-25 23:51 UTCEG score recompute
  55. 2026-06-25 23:50 UTCNVD updatefirst tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-11800?
CVE-2026-11800 is a high vulnerability published on June 25, 2026. A flaw was found in Keycloak. This JWT algorithm confusion vulnerability in the JWT Authorization Grant flow allows an attacker with valid client credentials to bypass signature verification. By forging an assertion, the attacker can create unauthorized access tokens. This enables the attacker to…
When was CVE-2026-11800 disclosed?
CVE-2026-11800 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11800 actively exploited?
CVE-2026-11800 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-11800?
CVE-2026-11800 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-11800?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11800, 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-11800

Explore →

Is Your Infrastructure Affected by CVE-2026-11800?

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

Start Free Scan →Browse All CVEs