CVE-2026-4282: Keycloak: keycloak: privilege escalation via forged authorization codes due to singleuseobjectprovider isolation flaw
A flaw was found in Keycloak. The SingleUseObjectProvider, a global key-value store, lacks proper type and namespace isolation. This vulnerability allows an unauthenticated attacker to forge authorization codes. Successful exploitation can lead to the creation of admin-capable access tokens, resulting in privilege escalation.
Security readout for executives and security teams
Plain-English summary
CVE-2026-4282 is a Keycloak flaw that can let an unauthenticated attacker forge login authorization codes. If successful, the attacker could obtain admin-capable access tokens. Because Keycloak often controls identity and application access, compromise can create broad business impact even though Red Hat rates attack complexity as high.
Executive priority
Treat this as high priority for identity platforms. It can affect administrative access and downstream applications, but available sources do not show active exploitation. Patch planning should focus first on internet-exposed, production, and privileged-realm Keycloak deployments.
Technical view
The issue is improper type and namespace isolation in Keycloak's SingleUseObjectProvider global key-value store. Red Hat says this can permit forged authorization codes and privilege escalation to admin-capable access tokens. The CVSS 3.1 score is 7.4, with network attack vector, no privileges, no user interaction, high complexity, and high confidentiality and integrity impact.
Likely exposure
Exposure appears limited to listed Red Hat build of Keycloak 26.2 and 26.4 packages and operator bundles. Source data marks Red Hat build of Keycloak 26.2.15 and 26.4.11 as unaffected, but package mapping is nuanced and should be confirmed against installed versions and RHSA advisories.
Exploitation context
The bundle does not cite active exploitation, and KEV is false. Exploitation is described as unauthenticated but high complexity. No public exploit steps are provided in the source bundle, and none should be assumed from the available evidence.
Researcher notes
Key analysis points are SingleUseObjectProvider isolation, authorization-code integrity, and token privilege outcome. The source bundle identifies CWE-653 and affected Red Hat package streams, but does not provide exploit mechanics, full patch details, or evidence of exploitation in the wild.
Mitigation direction
Identify all Red Hat build of Keycloak 26.2 and 26.4 deployments.
Review RHSA-2026:6475 through RHSA-2026:6478 for applicable updates.
Upgrade to vendor-designated unaffected builds where applicable.
Prioritize externally reachable or identity-critical Keycloak environments.
Monitor Red Hat CVE and Bugzilla pages for revised guidance.
Validation and detection
Inventory installed Keycloak package names and versions.
Compare deployments with Red Hat affected and unaffected product entries.
Confirm whether operator bundles are present and updated.
Review identity logs for unusual admin token issuance or authorization-code anomalies.
Verify remediation status against the relevant RHSA advisory.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-653: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
7Timeline events
2ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-653 · source CWE mapping
Improper Isolation or Compartmentalization
Improper Isolation or Compartmentalization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.