# CVE-2026-7571: Keycloak: keycloak: access token disclosure and implicit flow bypass via forged client data

> Attackers can bypass implicit flow restrictions to obtain unauthorized access tokens, leading to token disclosure in logs and headers.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 May 2026
- **Updated:** 20 May 2026
- **Also known as:** BIT-keycloak-2026-7571, ECHO-3445-2751-481d, GHSA-hq3p-w4xv-x7vp, MINI-978x-fgfc-8388, MINI-xvfj-j6fw-m8vj

## What is CVE-2026-7571?

CVE-2026-7571 is a high-severity vulnerability in Redhat Build of Keycloak, published on 19 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-472 (External Control of Assumed-Immutable Web Parameter)

## Which versions are affected by CVE-2026-7571?

3 open source packages ship an affected version, including org.keycloak:keycloak-services and keycloak. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-services` | Maven | All versions | 26.6.2 |
| `org.keycloak:keycloak-services` | Maven | All versions | 26.6.2 |
| `keycloak` | Bitnami | From 26.4.0 | 26.4.12 |

Products: Redhat Build of Keycloak.

## How do I fix CVE-2026-7571?

Upgrade org.keycloak:keycloak-services to 26.6.2 or later.

## Is CVE-2026-7571 being exploited?

There is no known exploitation of CVE-2026-7571 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Build of Keycloak

- [CVE-2026-15572](https://insights.sbomify.com/CVE-2026-15572/): Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation (high 8.8)
- [CVE-2026-3047](https://insights.sbomify.com/CVE-2026-3047/): Keycloak SAML Broken has Authentication Bypass by Primary Weakness (high 8.8)
- [CVE-2026-15573](https://insights.sbomify.com/CVE-2026-15573/): Keycloak-services: keycloak-services: authorization bypass via unnormalized uri matching in pathmatcher (high 8.1)
- [CVE-2026-16102](https://insights.sbomify.com/CVE-2026-16102/): Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers (high 8.1)
- [CVE-2026-1609](https://insights.sbomify.com/CVE-2026-1609/): Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7571 and fix it if it is affected.

What it is: CVE-2026-7571 is a high-severity vulnerability in Redhat Build of Keycloak, published on 19 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7571 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.6.2
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.6.2
- keycloak (Bitnami): affected from 26.4.0; fixed in 26.4.12

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7571/ (Markdown: https://insights.sbomify.com/CVE-2026-7571/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7571
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7571
- OSV: https://osv.dev/vulnerability/CVE-2026-7571

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7571/
Summaries are generated and may contain mistakes; the official description above is the record.