CVE-2026-16093

Keycloak-services: keycloak-services: required signed-jwt assertion policy can be bypassed with unsigned assertion headers

State
Published
Severity
5.4 Medium
Published
Jul 17, 2026
Updated
Sep 16, 2026
Reserved
Jul 17, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.15.4 MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:Nredhat

Weaknesses

  • CWE-807 Reliance on Untrusted Inputs in a Security Decision

Affected Products

ProductVersions
Red Hat build of Keycloak 26.6Red Hat
  • 26.6.7-3 and laterNot affected
Red Hat build of Keycloak 26.6Red Hat
  • 26.6-20 and laterNot affected
Red Hat build of Keycloak 26.6Red Hat
  • 26.6-20 and laterNot affected
Red Hat build of Keycloak 26.6.7Red Hat
    Red Hat build of Keycloak 26.6.7Red Hat
      Red Hat build of Keycloak 26.6.7Red Hat
        Red Hat Data Grid 8Red Hat
          Red Hat JBoss Enterprise Application Platform Expansion PackRed Hat
            Red Hat Single Sign-On 7Red Hat

              References

              Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.