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.
Published: 2026-07-17
Score: 5.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Keycloak’s Client Policies enforce requirements such as signed JWTs for authentication. Due to a flaw, the system accepts unsigned assertions and receives them as signed, enabling any client with valid credentials to use plain client secrets in place of the mandated signed JWT. This bypass results in an authentication bypass that undermines the administrator’s security policy, potentially allowing an attacker to obtain access to protected resources.

Affected Systems

Vulnerable products include Red Hat Build of Keycloak, Red Hat Data Grid 8, Red Hat JBoss Enterprise Application Platform Expansion Pack, and Red Hat Single Sign‑On 7. No specific affected versions were supplied by the CNA, so all currently deployed releases of these products are considered potentially impacted.

Risk and Exploitability

With a CVSS score of 5.4, the vulnerability represents medium severity. The EPSS score of less than 1% indicates a very low likelihood of exploitation, though it is not present in the CISA KEV catalog. The attack requires possession of legitimate client credentials and the ability to send crafted assertion a moderate risk if the policy enforcement is a critical control in their environment.

Generated by OpenCVE AI on July 31, 2026 at 00:03 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply vendor-supplied patches or where the signed‑JWT enforcement logic is corrected.
  • Verify the Client Policies configuration to confirm that signed‑JWT enforcement is active by testing authentication with both signed and unsigned assertions.
  • If a timely upgrade is not possible, limit exposure by revoking unnecessary client credentials, reducing network reach to the authentication endpoint, and monitoring for anomalous authentication attempts.

Generated by OpenCVE AI on July 31, 2026 at 00:03 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 28 Jul 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Redhat build Of Keycloak
Redhat data Grid
Redhat jboss Enterprise Application Platform Expansion Pack
Vendors & Products Redhat build Of Keycloak
Redhat data Grid
Redhat jboss Enterprise Application Platform Expansion Pack

Tue, 21 Jul 2026 02:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Sat, 18 Jul 2026 12:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Moderate


Fri, 17 Jul 2026 16:45:00 +0000

Type Values Removed Values Added
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.
Title Keycloak-services: keycloak-services: required signed-jwt assertion policy can be bypassed with unsigned assertion headers
First Time appeared Redhat
Redhat build Keycloak
Redhat jboss Data Grid
Redhat jbosseapxp
Redhat red Hat Single Sign On
Weaknesses CWE-807
CPEs cpe:/a:redhat:build_keycloak:
cpe:/a:redhat:jboss_data_grid:8
cpe:/a:redhat:jbosseapxp
cpe:/a:redhat:red_hat_single_sign_on:7
Vendors & Products Redhat
Redhat build Keycloak
Redhat jboss Data Grid
Redhat jbosseapxp
Redhat red Hat Single Sign On
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}


Subscriptions

Redhat Build Keycloak Build Of Keycloak Data Grid Jboss Data Grid Jboss Enterprise Application Platform Expansion Pack Jbosseapxp Red Hat Single Sign On
cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2026-07-21T01:45:52.870Z

Reserved: 2026-07-17T14:08:34.722Z

Link: CVE-2026-16093

cve-icon Vulnrichment

Updated: 2026-07-21T01:45:45.671Z

cve-icon NVD

No data.

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-07-16T17:01:13Z

Links: CVE-2026-16093 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-07-31T00:15:05Z

Weaknesses
  • CWE-807

    Reliance on Untrusted Inputs in a Security Decision