Keycloak-services: keycloak-services: cross-realm client read/write via request-level cache missing realm ownership check
Severity and exploitation
KEV coverage does not rule out exploitation.
Assessment vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:LSeverity
medium5.5CVSS measures technical severity, not the likelihood of an attack.
Known exploitation
Not listed in the checked CISA KEV catalog
Absence from CISA KEV does not rule out attacks.
Public exploit
Not established by this record
Missing evidence does not mean no public exploit exists.
Remediation
Source guidance available
Review the recorded instructions. Guidance may be a workaround rather than a fixed version.
What this means
A flaw in Keycloak's Admin REST API allows an administrator with limited privileges to read or modify sensitive client configurations. The issue occurs due to a missing realm ownership check in the request-level cache. Successful exploitation could expose client credentials or redirect administrative login attempts.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Attack conditions
No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.
Review supporting sources →Affected versions
Check the exact model, release, and any platform requirements against your installation.
Red Hat · redhat
Red Hat build of Keycloak 26.6.8
0 ranges
Red Hat · redhat
Red Hat build of Keycloak 26.6.8
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: unaffected
Product identifiers (CPE)
cpe:/a:redhat:build_keycloak:26.6::el9Red Hat · redhat
Red Hat build of Keycloak 26.6.8
0 ranges
Red Hat · redhat
Red Hat build of Keycloak 26.6.8
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: unaffected
Product identifiers (CPE)
cpe:/a:redhat:build_keycloak:26.6::el9Red Hat · redhat
Red Hat build of Keycloak 26.6.8
0 ranges
Red Hat · redhat
Red Hat build of Keycloak 26.6.8
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: unaffected
Product identifiers (CPE)
cpe:/a:redhat:build_keycloak:26.6::el9Red Hat · redhat
Red Hat Single Sign-On 7
0 ranges
Red Hat · redhat
Red Hat Single Sign-On 7
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: unaffected
Product identifiers (CPE)
cpe:/a:redhat:red_hat_single_sign_on:7What to do
Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.
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.
cve.new guidance unless attributed to a publisher. This page does not inspect your installation.
Public exploit evidence
No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.
Original source description
Read the full publisher description
A flaw was found in the Admin REST API of Keycloak, an open-source identity and access management solution. The issue occurs because the API uses a per-request in-memory cache to resolve clients by their unique identifier without verifying if the client belongs to the realm specified in the request path. This allows an administrator with limited privileges to read or modify sensitive client configurations in the master realm by accessing them through a realm they control. Successful exploitation could lead to the exposure of client credentials or the redirection of administrative login attempts to malicious sites.
References
3 sourcesInside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-94215View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
Timeline
All times UTCAdvisory published
Publication date supplied by the source.
Source updated
Latest modification date supplied by the source.
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.