Severity by source
AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
Network-reachable and unauthenticated (AV:N/PR:N), but requires non-default CRL/OCSP revocation config so AC:H; scope changes to internal systems (S:C); blind SSRF yields only limited confidentiality (C:L), no I/A impact.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
Lifecycle Timeline
2DescriptionCVE.org
A flaw was found in the X.509 client-certificate authenticator of Keycloak, a solution for identity and access management. The issue occurs when the server is configured to check certificate revocation using CRL Distribution Points or OCSP. An attacker can provide a specially crafted certificate that points to a malicious server, causing Keycloak to make unauthorized outbound requests to internal or external endpoints before the certificate is fully validated. This can lead to a blind server-side request forgery (SSRF) attack.
AnalysisAI
Blind server-side request forgery in the X.509 client-certificate authenticator of Keycloak (and the downstream Red Hat Build of Keycloak and Red Hat Single Sign-On 7) lets an unauthenticated remote attacker induce the server to make outbound requests to URLs specified in a crafted client certificate, before that certificate has been fully validated. The flaw is reachable only when X.509 client-certificate authentication is enabled and certificate revocation checking via CRL Distribution Points or OCSP is configured - a non-default setup, which is why the assessed vector carries AC:H despite PR:N/UI:N. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
No credit card · 7-day full trial
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires that Keycloak/RH-SSO be configured for X.509 client-certificate authentication AND that certificate revocation checking is enabled via CRL Distribution Points or OCSP; without this non-default configuration the flaw is not reachable. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a genuinely low-to-moderate priority issue, not a top-tier emergency, and the signals are largely consistent. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Patch availability is not confirmed in the supplied intelligence - no vendor-released fixed version is specified, so administrators should monitor the Red Hat advisory (https://access.redhat.com/security/cve/CVE-2026-105301) and Bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=2545797) and upgrade to the patched Keycloak / Red Hat Build of Keycloak / RH-SSO 7 build as soon as it is published; there is no vendor-released patch identified at time of analysis. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
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
Mismatched handling of the HTTP/1 absolute-form request authority in Red Hat build of Quarkus and other affected Red Hat
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
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-92255
GHSA-hg66-m76j-q2rm