# CVE-2026-4325: Keycloak: keycloak: replay of action tokens via improper handling of single-use entries

> Attackers can replay consumed action tokens like password reset links by deleting single-use entries, leading to unauthorized account access.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** BIT-keycloak-2026-4325, ECHO-5364-0e4b-b4fd, GHSA-rx66-hj7g-28h7, MINI-4wr7-pqcx-g9r6, MINI-pw88-v49h-49ph

## What is CVE-2026-4325?

CVE-2026-4325 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A flaw was found in Keycloak. The SingleUseObjectProvider, a global key-value store, lacks proper type and namespace isolation. This vulnerability allows an attacker to delete arbitrary single-use entries, which can enable the replay of consumed action tokens, such as password reset links. This could lead to unauthorized access or account compromise.

Weakness: CWE-653 (Improper Isolation or Compartmentalization)

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

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.5.7 |
| `org.keycloak:keycloak-services` | Maven | All versions | 26.5.7 |
| `keycloak` | Bitnami | From 26.2.0 | 26.2.1, 26.3.0, 26.4.1, 26.5.0 |

Products: Redhat Build of Keycloak.

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

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

## Is CVE-2026-4325 being exploited?

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

What it is: CVE-2026-4325 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-4325 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.5.7
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.5.7
- keycloak (Bitnami): affected from 26.2.0; fixed in 26.2.1, 26.3.0, 26.4.1, 26.5.0

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

## Sources

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

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