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.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

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.1(medium)
EPSS
26.4%
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
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-7571
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:19597
redhat Patch Available
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 / EcosystemFixed in / 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 rangeFixed inDependents
org.keycloak:keycloak-services1.0-alpha-1 ... 9.0.3 (226 versions)26.6.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 74× 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 148 total refreshes for this CVE.

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

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 in the National Vulnerability Database 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 26.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-7571?
CVE-2026-7571 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-7571?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7571, 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

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.

Start Free Scan →Browse All CVEs