Description
A flaw was found in Keycloak. When a JSON Web Encryption (JWE) encrypted request object is submitted, Keycloak may incorrectly process unsigned claims if the decrypted content is raw JSON, bypassing the configured signature policy. This allows a remote attacker to submit unauthorized claims, leading to a compromise of data integrity within the OpenID Connect (OIDC) authorization flow. While a redirect URI allowlist acts as a compensating control, this vulnerability violates OIDC Core and Financial-grade API (FAPI) signing requirements.
Published: 2026-05-28
Score: 5.9 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A flaw in Keycloak allows the JWE‑encrypted request object to be processed incorrectly when the decrypted payload is raw JSON. In this situation the system may treat unsigned claims as if they were signed, thereby bypassing the configured signature policy for OIDC request objects. This flaw enables a remote attacker to inject unauthorized claims into the authorization flow, compromising the integrity of the data exchanged during authentication and authorization.

Affected Systems

The vulnerability affects Red Hat Build of Keycloak. No specific version ranges are listed in the current data.

Risk and Exploitability

The CVSS score of 5.9 suggests a moderate risk. The EPSS score is unavailable and the vulnerability has not been listed in the CISA KEV catalog. Based on the description, the likely attack vector is remote over HTTPS request to the Keycloak server; an attacker can craft a JWE request object with unsigned claims and submit it to the authorization endpoint. Compromise is limited to data integrity within the OIDC flow and does not expose credentials or allow arbitrary code execution.

Generated by OpenCVE AI on May 28, 2026 at 05:23 UTC.

Remediation

Vendor Workaround

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.


OpenCVE Recommended Actions

  • Apply the latest patch or upgrade to an updated Red Hat Build of Keycloak that closes the JWE processing flaw
  • If a patch is not yet available, implement additional client‑side or proxy validation that rejects unsigned claims in JWE request objects
  • Continuously monitor OIDC request logs for anomalous or unauthorized claim patterns and flag them for investigation

Generated by OpenCVE AI on May 28, 2026 at 05:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 28 May 2026 04:45:00 +0000

Type Values Removed Values Added
Description A flaw was found in Keycloak. When a JSON Web Encryption (JWE) encrypted request object is submitted, Keycloak may incorrectly process unsigned claims if the decrypted content is raw JSON, bypassing the configured signature policy. This allows a remote attacker to submit unauthorized claims, leading to a compromise of data integrity within the OpenID Connect (OIDC) authorization flow. While a redirect URI allowlist acts as a compensating control, this vulnerability violates OIDC Core and Financial-grade API (FAPI) signing requirements.
Title Keycloak: keycloak: security policy bypass in jwe-encrypted request object processing
First Time appeared Redhat
Redhat build Keycloak
Weaknesses CWE-347
CPEs cpe:/a:redhat:build_keycloak:
Vendors & Products Redhat
Redhat build Keycloak
References
Metrics cvssV3_1

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


Subscriptions

Redhat Build Keycloak
cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2026-05-28T03:44:17.854Z

Reserved: 2026-05-28T03:11:57.675Z

Link: CVE-2026-9793

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-05-28T05:16:40.697

Modified: 2026-05-28T05:16:40.697

Link: CVE-2026-9793

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-28T05:30:06Z

Weaknesses