CVSS 3.1
7.1 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:NHigh (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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:Norg.keycloak:keycloak-services (Maven): fixed in 26.6.2Explain 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.
From the CNA's record in the CVE List.
| Product | Fixed in |
|---|---|
| Red Hat build of Keycloak 26.4 | 26.4.12-1 |
| Red Hat build of Keycloak 26.4 | 26.4-17 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-hq3p-w4xv-x7vp | Maven | org.keycloak:keycloak-services | <26.6.2 | 26.6.2 |
Red Hat rates this Moderate.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat build of Keycloak 26.4 | rhbk/keycloak-operator-bundle:26.4.12-1 | Fixed 2026-05-20 | RHSA-2026:19597 |
| Red Hat build of Keycloak 26.4 | rhbk/keycloak-rhel9:26.4-17 | Fixed 2026-05-20 | RHSA-2026:19597 |
| Red Hat build of Keycloak 26.4 | rhbk/keycloak-rhel9-operator:26.4-17 | Fixed 2026-05-20 | RHSA-2026:19597 |
| Red Hat build of Keycloak 26.4.12 | rhbk/keycloak-rhel9-operator | Fixed 2026-05-20 | RHSA-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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.