Description
Keycloak provides a mechanism called Client Policies to enforce security requirements on clients, such as requiring them to use signed JWTs for authentication. A flaw was discovered where this enforcement can be bypassed. An attacker with valid client credentials can provide a fake, unsigned assertion header that tricks the system into thinking the policy requirements have been met. This allows the attacker to authenticate using simpler methods like a client secret even when the administrator has mandated more secure, signed assertions.
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| Red Hat | Red Hat build of Keycloak 26.6 | — |
| Red Hat | Red Hat build of Keycloak 26.6 | — |
| Red Hat | Red Hat build of Keycloak 26.6 | — |
| Red Hat | Red Hat build of Keycloak 26.6.7 | — |
| Red Hat | Red Hat build of Keycloak 26.6.7 | — |
| Red Hat | Red Hat build of Keycloak 26.6.7 | — |
| Red Hat | Red Hat Data Grid 8 | — |
| Red Hat | Red Hat JBoss Enterprise Application Platform Expansion Pack | — |
| Red Hat | Red Hat Single Sign-On 7 | — |
References
Timeline
- Published
- Jul 17, 2026
- Last modified
- Sep 16, 2026
- NVD status
- Modified