cve.bz

CVE-2026-7571 redhat build of keycloak

7.1 highEPSS 0.4%Fix available

High (7.1) in redhat build of keycloak. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.keycloak:keycloak-services 26.6.2.

On this page
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.

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-472 External Control of Assumed-Immutable Web Parameter
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-7571 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-7571?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-7571?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-7571 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-7571

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-7571](https://cve.bz/cve/badge/CVE-2026-7571.svg)](https://cve.bz/cve/CVE-2026-7571)

HTML:

<a href="https://cve.bz/cve/CVE-2026-7571"><img src="https://cve.bz/cve/badge/CVE-2026-7571.svg" alt="CVE-2026-7571"></a>

Affected

Versions

From the CNA's record in the CVE List.

Fixed in

ProductFixed in
Red Hat build of Keycloak 26.426.4.12-1
Red Hat build of Keycloak 26.426.4-17

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-hq3p-w4xv-x7vpMavenorg.keycloak:keycloak-services<26.6.226.6.2

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This High severity flaw in Keycloak allows a low-privilege user, with knowledge of user credentials and client ID, to bypass the `implicitFlowEnabled=false` setting. By forging client data during a session restart, an attacker can obtain an implicit access token, potentially exposing it in URL query strings if `response_mode=query` is also forged. This bypass undermines a critical security control intended to prevent implicit flow, leading to unauthorized access to sensitive tokens.

Red Hat's mitigation

To mitigate this issue, restrict network access to the Keycloak authentication endpoint to trusted clients and networks. Implement firewall rules to control inbound connections to the Keycloak service ports, thereby reducing the attack surface and limiting who can initiate authentication flows and potentially exploit the implicit flow bypass. If the Keycloak service is reloaded or restarted, ensure these network restrictions remain in effect.

ProductPackageStateAdvisory
Red Hat build of Keycloak 26.4rhbk/keycloak-operator-bundle:26.4.12-1Fixed 2026-05-20RHSA-2026:19597
Red Hat build of Keycloak 26.4rhbk/keycloak-rhel9:26.4-17Fixed 2026-05-20RHSA-2026:19597
Red Hat build of Keycloak 26.4rhbk/keycloak-rhel9-operator:26.4-17Fixed 2026-05-20RHSA-2026:19597
Red Hat build of Keycloak 26.4.12rhbk/keycloak-rhel9-operatorFixed 2026-05-20RHSA-2026:19596

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-7571.

Attack patterns (CAPEC)

  • CAPEC-31 Accessing/Intercepting/Modifying HTTP Cookies Likelihood: High · Severity: High
  • CAPEC-39 Manipulating Opaque Client-based Data Tokens Likelihood: High · Severity: Medium
  • CAPEC-146 XML Schema Poisoning Likelihood: Low · Severity: High
  • CAPEC-226 Session Credential Falsification through Manipulation Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON