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 high-severity Keycloak flaw where weak separation inside a single-use key-value store can let an unauthenticated attacker forge authorization codes. If successful, this can produce admin-capable access tokens and escalate privileges in affected Red Hat build of Keycloak deployments.
Executive priority
Treat this as a near-term patching priority for Keycloak-backed authentication services. A successful exploit can affect privileged access, but available sources do not confirm active exploitation. Prioritize externally reachable and admin-critical environments first.
Technical view
Red Hat describes improper type and namespace isolation in Keycloak SingleUseObjectProvider. The issue can allow forged authorization codes and admin-capable token creation. CVSS 3.1 is 7.4: network reachable, high complexity, no privileges, no user interaction, with high confidentiality and integrity impact.
Likely exposure
Exposure is limited by the provided data to affected Red Hat build of Keycloak 26.2 and 26.4 package entries. Internet-facing identity providers, admin realms, and environments relying on Keycloak for privileged application access carry higher business risk.
Exploitation context
The CVE is not listed as KEV in the source bundle, and no cited source states active exploitation. The attack is unauthenticated and network-based but rated high complexity, so urgency is serious but should not be treated as confirmed mass exploitation.
Researcher notes
The root issue is CWE-653 involving isolation failure in SingleUseObjectProvider. The source bundle does not provide exploit mechanics, indicators, or non-Red Hat product impact. Version mapping is package-specific, so validation should use Red Hat advisories and CSAF data rather than product-name assumptions.
Mitigation direction
Apply the relevant Red Hat RHSA updates for affected Keycloak packages.
Prioritize Red Hat build of Keycloak 26.2 and 26.4 deployments.
Confirm whether fixed or unaffected builds 26.2.15 or 26.4.11 apply to your channel.
Restrict administrative access paths while patching is scheduled.
Monitor vendor guidance for package-specific remediation details.
Validation and detection
Inventory all Red Hat build of Keycloak deployments and package versions.
Compare installed packages with Red Hat affected and unaffected entries.
Confirm RHSA-2026:6475 through RHSA-2026:6478 applicability.
Review logs for unexplained admin-capable token issuance.
Check whether public identity endpoints expose affected deployments.
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.