Keycloak SingleUseObjectProvider improper isolation or compartmentalization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 1.33- |
Summary
A vulnerability classified as problematic has been found in Keycloak. Affected by this vulnerability is an unknown functionality of the component SingleUseObjectProvider. This manipulation causes improper isolation or compartmentalization. This vulnerability is handled as CVE-2026-4325. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as problematic was found in Keycloak (version now known). Affected by this vulnerability is some unknown processing of the component SingleUseObjectProvider. The manipulation with an unknown input leads to a improper isolation or compartmentalization vulnerability. The CWE definition for the vulnerability is CWE-653. The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions. As an impact it is known to affect integrity. The summary by CVE is:
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.
It is possible to read the advisory at access.redhat.com. This vulnerability is known as CVE-2026-4325 since 03/17/2026. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/02/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.1
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (redhat): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper isolation or compartmentalizationCWE: CWE-653
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/17/2026 CVE reserved04/02/2026 Advisory disclosed
04/02/2026 VulDB entry created
04/02/2026 VulDB entry last update
Sources
Advisory: RHSA-2026:6477Status: Not defined
CVE: CVE-2026-4325 (🔒)
GCVE (CVE): GCVE-0-2026-4325
GCVE (VulDB): GCVE-100-354871
Entry
Created: 04/02/2026 16:53Changes: 04/02/2026 16:53 (60)
Complete: 🔍
Cache ID: 216:4A9:103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.