# CVE-2026-8922: Org.keycloak/keycloak-services: keycloak: org.keycloak.protocol.oidc: security flaw in org.keycloak/keycloak-services

> Keycloak fails to honor realm-level token revocation policies during OIDC introspection, allowing revoked tokens to remain active and enabling unauthorized access.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 26 Jun 2026
- **Also known as:** ECHO-a65a-c6e8-0f1d, GHSA-83c4-ffjp-mxp9, MINI-29gw-p694-49pm, MINI-w7gq-g2p6-5ffw

## What is CVE-2026-8922?

CVE-2026-8922 is a medium-severity authentication bypass 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. When both realm-level and client-level `notBefore` revocation policies are configured, Keycloak's OpenID Connect (OIDC) Introspection feature fails to properly honor the realm-level policy. This allows tokens that should have been revoked to remain active, potentially leading to unauthorized access or continued session validity. This could impact the security of systems utilizing Keycloak for identity and access management.

Weakness: CWE-303 (Incorrect Implementation of Authentication Algorithm)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-services` | Maven | All versions to 26.6.2 | None |
| `org.keycloak:keycloak-services` | Maven | All versions to 26.6.2 | None |

Products: Redhat Build of Keycloak.

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

Apply the vendor's patch.

## Is CVE-2026-8922 being exploited?

There is no known exploitation of CVE-2026-8922 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-8922 and fix it if it is affected.

What it is: CVE-2026-8922 is a medium-severity authentication bypass 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-8922 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions up to 26.6.2; no fix listed
- org.keycloak:keycloak-services (Maven): affected all versions up to 26.6.2; no fix listed

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-8922/ (Markdown: https://insights.sbomify.com/CVE-2026-8922/index.md)
```

## Sources

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

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