CVE-2026-4325
Redhat Build Of Keycloak 26.2 … 26.4.11
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:NSummary
CVE-2026-4325 is a medium-severity Improper Isolation or Compartmentalization (CWE-653) vulnerability in Redhat Build Of Keycloak. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 17th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-3 (Security Function Isolation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-18210
Vulnerability Data
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…
more
reset links. This could lead to unauthorized access or account compromise.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vulnerability bypasses single-use token enforcement in Keycloak auth flows, directly enabling replay of action tokens for account access (T1078 Valid Accounts) and manipulation of authentication mechanisms (T1556 Modify Authentication Process).
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces namespace- and type-specific access rules on the SingleUseObjectProvider so that only authorized operations on specific token entries are permitted, blocking arbitrary deletion.
Requires isolation of the single-use token store's security functions and data structures, preventing the global KV store from allowing cross-namespace or cross-type interference that enables token replay.
Enforces information-flow policies between distinct token namespaces/types inside the provider, stopping unauthorized deletion or reuse of consumed action tokens across compartment boundaries.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Segregation of duties directly enforces separation of privilege levels and functions.
Network segregation is a classic technical control for isolating different privilege domains.
Secure system architecture principles explicitly call for isolation and least-privilege boundaries.
Separation of development, test and production environments is a direct application of compartmentalization.
Access control policies establish the boundaries that isolation must enforce.
Managing access rights is the operational mechanism for compartmentalizing privileges.