EUVD-2026-39476
GHSA-7pm9-g8jh-3m74
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Realm admin role required (PR:H); network API accessible (AV:N); impact is read-only filesystem probing with no integrity or availability effect.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
Lifecycle Timeline
1DescriptionCVE.org
A flaw was found in Keycloak. A realm administrator with the "manage-realm" role can exploit this vulnerability by submitting an arbitrary filesystem path as a keystore parameter when creating a key provider component. This allows the administrator to probe arbitrary filesystem paths, determining which files exist and are readable by the Keycloak process. This information disclosure could be used to identify high-value targets for follow-on attacks.
AnalysisAI
Red Hat Build of Keycloak allows realm administrators holding the 'manage-realm' role to probe arbitrary filesystem paths by submitting unsanitized path values as keystore parameters during key provider component creation. The Keycloak process's file access attempt reveals whether a given path exists and is readable, functioning as a filesystem oracle for authenticated attackers. No public exploit code or active exploitation has been identified at time of analysis; the CVSS score of 4.9 (PR:H) reflects the significant constraint of requiring realm administrator credentials prior to exploitation.
Technical ContextAI
Keycloak is an open-source Identity and Access Management (IAM) platform distributed commercially as Red Hat Build of Keycloak. Its realm administration interface exposes an API for configuring cryptographic key provider components, which accepts filesystem paths to keystores. The root cause is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory, or Path Traversal): the keystore path parameter is not validated or sandboxed against a permitted directory before the Keycloak process attempts to access it. Because Keycloak may run with elevated OS-level permissions to access its own keystores, this path traversal exposes any file readable by the Keycloak service account. The affected CPE (cpe:2.3:a:red_hat:red_hat_build_of_keycloak:*:*:*:*:*:*:*:*) uses a wildcard version field, indicating Red Hat has not bounded the affected version range in the CPE data.
RemediationAI
Consult the Red Hat Security Advisory at https://access.redhat.com/security/cve/CVE-2026-9083 for the official patch; a specific fixed version number was not confirmed in the provided input data, so a precise upgrade target cannot be stated here. In the interim, restrict the 'manage-realm' role to the minimum set of fully trusted administrators, as this role is the prerequisite for exploitation - reducing its assignment scope directly limits the attack surface. Audit existing realm administrators and revoke the 'manage-realm' role from any accounts that do not strictly require key provider management capabilities. Where Keycloak is deployed in multi-tenant environments, consider deploying separate Keycloak instances per tenant to limit blast radius if a realm admin account is compromised. Running the Keycloak process under a minimally privileged OS service account reduces the set of filesystem paths that can be probed, though this is a depth-in-defense measure, not a fix. Monitor admin API activity for key provider creation requests with anomalous or unexpected path values as a detection control.
More in Red Hat Build Of Keycloak
View allAccount takeover in Red Hat Build of Keycloak allows an unauthenticated attacker to abuse the reset-credentials flow in
Account takeover in Keycloak (Red Hat build of Keycloak, Red Hat Single Sign-On 7) arises because the IdP-initiated SAML
Authentication bypass in Red Hat Build of Keycloak (and Red Hat Single Sign-On 7) lets an unauthenticated attacker forge
Privilege escalation in Red Hat Build of Keycloak's Dynamic Client Registration (DCR) grants an attacker with low-privil
Authorization bypass in the Keycloak Policy Enforcer allows any authenticated user to circumvent all enforced access con
URI normalization bypass in Keycloak's Authorization Services PathMatcher allows authenticated low-privilege users to re
Privilege escalation in Keycloak's Dynamic Client Registration (DCR) component allows attackers with standard user accou
Token exchange in Keycloak bypasses Google Workspace domain allowlist restrictions, enabling any valid Google account ho
Signature-verification bypass in Keycloak (and Red Hat's Keycloak-based products such as Red Hat Single Sign-On 7 and Re
Tenant-restriction bypass in Keycloak's Microsoft identity provider integration allows attackers holding any valid Micro
Session hijacking via SAML assertion replay in Keycloak's SAML broker component allows adjacent-network attackers to aut
Open redirect in Red Hat build of Keycloak permits remote attackers to send victims to attacker-controlled hosts by abus
Same weakness CWE-22 – Path Traversal
View allSame technique Information Disclosure
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today