CVE-2026-4282 json
Keycloak: keycloak: privilege escalation via forged authorization codes due to singleuseobjectprovider isolation flaw
published 2026-04-02 7 mo ago modified 2026-10-26 13 d ago also BIT-keycloak-2026-4282 , EUVD-2026-18208 , GHSA-hj93-h7pg-fh6v
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.keycloak:keycloak-services 26.5.7
- bitnami keycloak 26.2.1, 26.3.0, 26.4.1, 26.5.0
- Red Hat Red Hat build of Keycloak 26.2 26.2-18, 26.2.15-1
- Red Hat Red Hat build of Keycloak 26.4 26.4-14, 26.4.11-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-4282 updated cvss 7.4
keycloak: Keycloak: Privilege escalation via forged authorization codes due to SingleUseObjectProvider isolation flaw
-
Red Hat build of Keycloak 26.2 rhbk/keycloak-rhel9 26.2-18, rhbk/keycloak-rhel9-operator 26.2-18, rhbk/keycloak-operator-bundle 26.2.15-1fixed: vendor fix RHSA-2026:6476
-
Red Hat build of Keycloak 26.2.15fixed: vendor fix RHSA-2026:6475
-
Red Hat build of Keycloak 26.4 rhbk/keycloak-rhel9 26.4-14, rhbk/keycloak-rhel9-operator 26.4-14, rhbk/keycloak-operator-bundle 26.4.11-1fixed: vendor fix RHSA-2026:6478
-
Red Hat build of Keycloak 26.4.11fixed: vendor fix RHSA-2026:6477
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 7 mo ago
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| CISA ADP | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| OSV | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.keycloak:keycloak-services | <26.5.7 |
26.5.7 |
| bitnami | keycloak | >=26.2.0, <26.2.1 >=26.2.15, <26.3.0 >=26.4.0, <26.4.1 >=26.4.11, <26.5.0 |
26.2.1 26.3.0 26.4.1 26.5.0 |
Affected products
- Red Hat Red Hat build of Keycloak 26.2
- Red Hat Red Hat build of Keycloak 26.2.15
- Red Hat Red Hat build of Keycloak 26.4
- Red Hat Red Hat build of Keycloak 26.4.11
Classification
- Weakness
-
- CWE-653 Improper Isolation or Compartmentalization
References
-
github.com
/keycloak/keycloak/commit/9046f201125a6fd6be9c116b99d348509d99d4a5
web
-
access.redhat.com
/errata/RHSA-2026:6475
vendor-advisory, web, advisory
-
access.redhat.com
/errata/RHSA-2026:6476
vendor-advisory, web, advisory
-
access.redhat.com
/errata/RHSA-2026:6477
vendor-advisory, web, advisory
-
access.redhat.com
/errata/RHSA-2026:6478
vendor-advisory, web, advisory
-
access.redhat.com
/security/cve/CVE-2026-4282
vdb-entry, web, vendor-advisory, advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=2448061
issue-tracking, web, vendor-advisory, advisory
-
security.access.redhat.com
/data/csaf/v2/vex/2026/cve-2026-4282.json
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-4282
advisory, web
-
github.com
/keycloak/keycloak/issues/47719
web
-
github.com
/keycloak/keycloak
package
Sources
- CVE List CVE-2026-4282
- GitHub Advisory GHSA-hj93-h7pg-fh6v
- NVD CVE-2026-4282
- OSV BIT-keycloak-2026-4282
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.