CVE-2026-4630

Keycloak: keycloak: unauthorized resource access and data modification via insecure direct object reference

Published May 19, 2026 CVSS 3.1 · 6.8 Medium EPSS < 1% KEV · Not listed
Description
A flaw was found in Keycloak. An authenticated client could exploit an Insecure Direct Object Reference (IDOR) vulnerability in the Authorization Services Protection API endpoint. By knowing or obtaining a resource's unique identifier (UUID) belonging to another Resource Server within the same realm, the client could bypass authorization checks. This allows the client to perform unauthorized GET, PUT, and DELETE operations on resources, leading to information disclosure and potential unauthorized modification or deletion of data.

Analysis

AI-generated

Technical impact

An authenticated client can exploit an Insecure Direct Object Reference vulnerability in Keycloak’s Authorization Services Protection API. By learning or guessing another resource server’s unique identifier (UUID) within the same realm, the client bypasses normal authorization checks and can retrieve, modify, or delete that resource. The flaw leads to unauthorized information disclosure and data alteration, compromising confidentiality and integrity of resources that the client should not be able to access.

Affected Systems

The vulnerability affects Red Hat Build of Keycloak. No specific affected version range is documented in the available data, so all deployments of this product could potentially be impacted until an official fix is released by Red Hat.

Risk and Exploitability

The CVSS score of 6.8 indicates a moderate severity, and the EPSS score is not reported, so the likelihood of widespread exploitation is unclear. Because the flaw requires an authenticated client that knows or discovers a resource UUID, the threat is most acute in environments where clients have broad read/write permissions or where resources are enumerated. The vulnerability is not listed in the CISA KEV catalog, suggesting it has not yet been exploited in the wild or at a large scale. Red Hat has stated that no workaround meets its security criteria, so organizations should consult Red Hat support for guidance and keep an eye out for an official patch.

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

  • Contact Red Hat support to determine if an update or interim guidance is available and to report any suspected exploitation
  • Configure client applications to request only the scopes and permissions strictly necessary for their function, and enforce Keycloak resource‑level permission checks to limit what operations they can perform on a given UUID
  • Implement monitoring of Authorization Services API usage to detect anomalous GET, PUT, or DELETE calls on resources and revoke access for any client exhibiting suspicious activity

Generated by OpenCVE AI on May 19, 2026 at 12:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-c739-f6xw-6pv2 Keycloak Protection API allows authenticated clients to access and modify resources owned by other Resource Servers
History
Type Values Removed Values Added
CPEs cpe:2.3:a:redhat:build_of_keycloak:*:*:*:*:*:*:*:*
Type Values Removed Values Added
CPEs cpe:/a:redhat:build_keycloak: cpe:/a:redhat:build_keycloak:26.4::el9
References
Type Values Removed Values Added
First Time appeared Redhat build Of Keycloak
Vendors & Products Redhat build Of Keycloak
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
Description A flaw was found in Keycloak. An authenticated client could exploit an Insecure Direct Object Reference (IDOR) vulnerability in the Authorization Services Protection API endpoint. By knowing or obtaining a resource's unique identifier (UUID) belonging to another Resource Server within the same realm, the client could bypass authorization checks. This allows the client to perform unauthorized GET, PUT, and DELETE operations on resources, leading to information disclosure and potential unauthorized modification or deletion of data.
Title Keycloak: keycloak: unauthorized resource access and data modification via insecure direct object reference
First Time appeared Redhat
Redhat build Keycloak
Weaknesses CWE-639
CPEs cpe:/a:redhat:build_keycloak:
Vendors & Products Redhat
Redhat build Keycloak
References
Metrics cvssV3_1

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

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
May 20, 2026, 4:08 PM
Reserved
Mar 23, 2026, 8:12 AM
Status
Analyzed
Published
May 19, 2026, 12:16 PM
Modified
Oct 26, 2026, 8:10 PM