# CVE-2026-4325: keycloak — Fixed in 26.2.1

📦 Bitnami

Not in CISA KEV

# CVE-2026-4325 — keycloak

CVE-2026-4325 is a CWE-653 vulnerability in keycloak. A fix is available for keycloak — see the affected versions and patch details below.

Keycloak: keycloak: replay of action tokens via improper handling of single-use entries

Also known as[GHSA-rx66-hj7g-28h7](/vulnerability/GHSA-rx66-hj7g-28h7)

Published

Aug 25, 2026

Updated

Sep 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-4325.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

0.00%0.30%0.61%0.91%0.0%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## Real-World Exposure

1 pkg affected

📦`keycloak`

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

## 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.

## Affected Packages

1 total 1 fixed

Ecosystem

Package

Vulnerable range

Fix

📦Bitnami

`keycloak` 

≥ 26.2.0&&< 26.2.1

26.2.1

## Affected Products

1 product · 5 configurations

Application

`build of keycloak`redhat

4 versions

26.226.2.1526.426.4.11

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keycloak, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update keycloak to 26.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-4325 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
    

## Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This flaw in Keycloak's SingleUseObjectProvider has a MODERATE impact. It allows an attacker to delete arbitrary single-use entries, which could lead to the replay of consumed action tokens such as password reset links. Exploitation requires high attack complexity and user interaction.

Workaround published by Red Hat

> Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: [Red Hat security advisory for CVE-2026-4325](https://access.redhat.com/security/cve/cve-2026-4325) (CC BY 4.0)

Product

Fixed in

Advisory

Red Hat build of Keycloak 26.2

`rhbk/keycloak-operator-bundle:26.2.15-1`

[RHSA-2026:6476](https://access.redhat.com/errata/RHSA-2026:6476)

Red Hat build of Keycloak 26.2.15

`rhbk/keycloak-rhel9`

[RHSA-2026:6475](https://access.redhat.com/errata/RHSA-2026:6475)

Red Hat build of Keycloak 26.4

`rhbk/keycloak-operator-bundle:26.4.11-1`

[RHSA-2026:6478](https://access.redhat.com/errata/RHSA-2026:6478)

Red Hat build of Keycloak 26.4.11

`rhbk/keycloak-rhel9`

[RHSA-2026:6477](https://access.redhat.com/errata/RHSA-2026:6477)

## Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

### Is CVE-2026-4325 in your dependencies?

Find it across Bitnami, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)