CVE-2026-7571

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.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: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in Keycloak. A low-privilege user, with knowledge of user credentials and client ID, can bypass a security control intended to disable the implicit flow in OpenID Connect (OIDC) clients. By manipulating client data during a session restart, an attacker can obtain an access token that should not be available. This vulnerability can also lead to the exposure of these access tokens in server logs, proxy logs, and HTTP Referrer headers, resulting in sensitive information disclosure.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

Published

May 19, 2026

Last Modified

June 3, 2026

Advisory Details (4)

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

2464263 – (CVE-2026-7571) CVE-2026-7571 keycloak: Keycloak: Access token disclosure and implicit flow bypass via forged client data

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

cve-details

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

Vendor Advisories for CVE-2026-7571(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 / EcosystemFix (by version range) / PatchReleasedSource
redhatrhbk/keycloak-rhel9-operator:26.4-172026-05-20redhat
redhatrhbk/keycloak-rhel9-operator2026-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-services1.0-alpha-1 ... 9.0.3 (226 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 6× 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 242 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 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:57 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:04 UTCEPSS rescore
  11. 2026-09-29 15:24 UTCEPSS rescore
  12. 2026-09-28 13:52 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-26 00:28 UTCEPSS rescore
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-22 16:01 UTCEPSS rescore
  19. 2026-09-21 21:09 UTCEPSS rescore
  20. 2026-09-20 20:16 UTCEPSS rescore
  21. 2026-09-18 19:28 UTCEPSS rescore
  22. 2026-09-16 14:08 UTCEPSS rescore
  23. 2026-09-16 05:15 UTCEPSS rescore
  24. 2026-09-15 03:12 UTCEPSS rescore
  25. 2026-09-15 03:12 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-06 13:48 UTCEPSS rescore
  5. 2026-09-04 05:07 UTCEPSS rescore
  6. 2026-09-02 14:12 UTCEPSS rescore
  7. 2026-09-01 13:54 UTCEPSS rescore
  8. 2026-09-01 04:40 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 19:18 UTCEPSS rescore
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-28 21:42 UTCEPSS rescore
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-24 14:18 UTCEPSS rescore
  18. 2026-08-23 17:08 UTCEG score recompute
  19. 2026-08-23 17:08 UTCVendor advisory
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-21 23:49 UTCEPSS rescore
  22. 2026-08-21 23:39 UTCEG score recompute
  23. 2026-08-21 23:39 UTCVendor advisory
  24. 2026-08-20 22:56 UTCEPSS rescore
  25. 2026-08-20 19:05 UTCEG score recompute
  26. 2026-08-20 19:05 UTCVendor advisory
  27. 2026-08-19 17:04 UTCEPSS rescore
  28. 2026-08-18 13:49 UTCEPSS rescore
  29. 2026-08-18 13:49 UTCEPSS rescore
  30. 2026-08-17 13:47 UTCEPSS rescore
  31. 2026-08-17 10:01 UTCEG score recompute
  32. 2026-08-17 10:01 UTCVendor advisory
  33. 2026-08-16 14:56 UTCEPSS rescore
  34. 2026-08-16 14:56 UTCEPSS rescore
  35. 2026-08-16 03:36 UTCEG score recompute
  36. 2026-08-16 03:36 UTCVendor advisory
  37. 2026-08-16 02:15 UTCEPSS rescore
  38. 2026-08-15 01:31 UTCEPSS rescore
  39. 2026-08-14 14:43 UTCVendor advisory
  40. 2026-08-14 02:08 UTCEG score recompute
  41. 2026-08-14 02:08 UTCVendor advisory
  42. 2026-08-13 22:00 UTCEPSS rescore
  43. 2026-08-13 00:41 UTCEG score recompute
  44. 2026-08-13 00:41 UTCVendor advisory
  45. 2026-08-12 13:51 UTCEPSS rescore
  46. 2026-08-12 12:06 UTCVendor advisory
  47. 2026-08-11 13:54 UTCEG score recompute
  48. 2026-08-11 13:54 UTCVendor advisory
  49. 2026-08-11 13:43 UTCEPSS rescore
  50. 2026-08-11 00:40 UTCEG score recompute
  51. 2026-08-11 00:40 UTCVendor advisory
  52. 2026-08-11 00:00 UTCEPSS rescore
  53. 2026-08-10 02:47 UTCVendor advisory
  54. 2026-08-09 14:12 UTCEG score recompute
  55. 2026-08-09 14:12 UTCVendor advisory
  56. 2026-08-09 13:47 UTCEPSS rescore
  57. 2026-08-09 01:37 UTCEG score recompute
  58. 2026-08-09 01:37 UTCVendor advisory
  59. 2026-08-08 16:37 UTCEPSS rescore
  60. 2026-08-08 02:22 UTCEG score recompute
  61. 2026-08-08 02:22 UTCVendor advisory
  62. 2026-08-07 13:47 UTCVendor advisory
  63. 2026-08-07 01:11 UTCEG score recompute
  64. 2026-08-07 01:11 UTCVendor advisory
  65. 2026-08-06 13:47 UTCEPSS rescore
  66. 2026-08-06 09:58 UTCVendor advisory
  67. 2026-08-05 21:23 UTCEG score recompute
  68. 2026-08-05 21:23 UTCVendor advisory
  69. 2026-08-05 19:17 UTCEPSS rescore
  70. 2026-08-05 19:17 UTCEPSS rescore
  71. 2026-08-04 15:10 UTCEPSS rescore
  72. 2026-08-04 10:39 UTCEPSS rescore
  73. 2026-08-04 05:38 UTCVendor advisory
  74. 2026-08-03 17:00 UTCEG score recompute
  75. 2026-08-03 17:00 UTCVendor advisory

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

Frequently asked(5)

What is CVE-2026-7571?
CVE-2026-7571 is a high vulnerability published on May 19, 2026. A flaw was found in Keycloak. A low-privilege user, with knowledge of user credentials and client ID, can bypass a security control intended to disable the implicit flow in OpenID Connect (OIDC) clients. By manipulating client data during a session restart, an attacker can obtain an access token…
When was CVE-2026-7571 disclosed?
CVE-2026-7571 was first published on May 19, 2026, with the most recent update on June 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-7571 actively exploited?
CVE-2026-7571 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-7571?
CVE-2026-7571 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-7571?
A fix for CVE-2026-7571 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-7571 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-7571

Explore →

Is Your Infrastructure Affected by CVE-2026-7571?

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

Book a Demo →Browse All CVEs