Unauthorized token claim injection via unchecked scope assignment
Published Jul 3, 2026 · Updated Jul 3, 2026
Authorization bypass in Red Hat build of Keycloak allows remote authenticated users to attach unauthorized scopes through the admin REST API. ClientResource assignment endpoints verify control of the target client but omit authorization checks for the referenced client-scope UUID. FGAP v2, delegated client-management rights, and knowledge of that UUID are required; attached scope mappers can add restricted claims to user tokens.
Summary
What happened
Authorization bypass in Red Hat build of Keycloak allows remote authenticated users to attach unauthorized scopes through the admin REST API. ClientResource assignment endpoints verify control of the target client but omit authorization checks for the referenced client-scope UUID. FGAP v2, delegated client-management rights, and knowledge of that UUID are required; attached scope mappers can add restricted claims to user tokens.
The record
- CVE
- CVE-2026-14614
- Published
- Jul 3, 2026
- Updated
- Jul 3, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-284, CWE-639
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 3, 2026CVE publishedPublication date reported by the CVE source.
- Jul 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo