Medium · published July 17, 2026
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.
| Product | Versions | Fixed in |
|---|---|---|
| redhat/build_of_keycloak | all versions | — |
| redhat/data_grid | all versions | — |
| redhat/jboss_enterprise_application_platform_expansion_pack | all versions | — |
| redhat/single_sign-on | all versions | — |