CVE-2026-4325: Improper Isolation or Compartmentalization in Red Hat Red Hat build of Keycloak 26.2
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.
AI Analysis
Technical Summary
The vulnerability in Red Hat build of Keycloak 26.2 involves improper isolation in the SingleUseObjectProvider component, which is responsible for managing single-use tokens. Due to lack of proper type and namespace isolation, an attacker can delete arbitrary single-use entries, allowing replay attacks on consumed action tokens such as password reset links. This can lead to unauthorized access or account compromise. The issue is tracked as CVE-2026-4325 with a CVSS 3.1 base score of 5.3 (medium severity). Red Hat has issued an important security advisory (RHSA-2026:6475 and RHSA-2026:6476) releasing updated Keycloak packages (26.2.15) that fix this vulnerability. The advisory recommends backing up existing installations before applying the update. The vulnerability affects the standalone Keycloak server and containerized OpenShift images. No exploits are currently known in the wild.
Potential Impact
Successful exploitation of this vulnerability allows an attacker to delete arbitrary single-use entries in the SingleUseObjectProvider, enabling replay of consumed action tokens such as password reset links. This can lead to unauthorized access or account compromise. The CVSS score of 5.3 reflects a medium severity impact with high integrity impact but no confidentiality or availability impact. There are no known exploits in the wild at the time of publication.
Mitigation Recommendations
Red Hat has released updated packages for Red Hat build of Keycloak version 26.2.15 that address this vulnerability. Users should back up their existing installations, including applications, configuration files, and databases, before applying the update. Applying the official update from Red Hat is the recommended remediation. There is no indication that any temporary workaround or mitigation is available or required beyond applying the update.
CVE-2026-4325: Improper Isolation or Compartmentalization in Red Hat Red Hat build of Keycloak 26.2
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Red Hat build of Keycloak 26.2 involves improper isolation in the SingleUseObjectProvider component, which is responsible for managing single-use tokens. Due to lack of proper type and namespace isolation, an attacker can delete arbitrary single-use entries, allowing replay attacks on consumed action tokens such as password reset links. This can lead to unauthorized access or account compromise. The issue is tracked as CVE-2026-4325 with a CVSS 3.1 base score of 5.3 (medium severity). Red Hat has issued an important security advisory (RHSA-2026:6475 and RHSA-2026:6476) releasing updated Keycloak packages (26.2.15) that fix this vulnerability. The advisory recommends backing up existing installations before applying the update. The vulnerability affects the standalone Keycloak server and containerized OpenShift images. No exploits are currently known in the wild.
Potential Impact
Successful exploitation of this vulnerability allows an attacker to delete arbitrary single-use entries in the SingleUseObjectProvider, enabling replay of consumed action tokens such as password reset links. This can lead to unauthorized access or account compromise. The CVSS score of 5.3 reflects a medium severity impact with high integrity impact but no confidentiality or availability impact. There are no known exploits in the wild at the time of publication.
Mitigation Recommendations
Red Hat has released updated packages for Red Hat build of Keycloak version 26.2.15 that address this vulnerability. Users should back up their existing installations, including applications, configuration files, and databases, before applying the update. Applying the official update from Red Hat is the recommended remediation. There is no indication that any temporary workaround or mitigation is available or required beyond applying the update.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- redhat
- Date Reserved
- 2026-03-17T12:43:33.403Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69ce6a44e6bfc5ba1dd993ab
Added to database: 4/2/2026, 1:08:20 PM
Last enriched: 4/9/2026, 10:30:50 PM
Last updated: 5/20/2026, 8:50:32 PM
Views: 97
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.