A flaw was found in Keycloak. An authenticated attacker can perform Server-Side Request Forgery (SSRF) by manipulating the `client_session_host` parameter during refresh token requests. This occurs when a Keycloak client is configured to use the `backchannel.logout.url` with the `application.session.host` placeholder. Successful exploitation allows the attacker to make HTTP requests from the Keycloak server’s network context, potentially probing internal networks or internal APIs, leading to information disclosure.
Security readout for executives and security teams
Plain-English summary
CVE-2026-4874 is a low-severity Keycloak SSRF issue. A logged-in attacker may cause Keycloak to send HTTP requests from the server’s network position, but only when a specific backchannel logout placeholder configuration is used. Impact is mainly limited information disclosure or internal network probing.
Executive priority
Treat as a planned patch and configuration review, not an emergency. Prioritize systems exposed to untrusted authenticated users or with broad internal network access. The business risk is unauthorized internal reconnaissance through a critical identity service.
Technical view
The flaw involves refresh token handling and manipulation of the client_session_host parameter. It applies when a Keycloak client uses backchannel.logout.url with the application.session.host placeholder. A successful authenticated request can trigger outbound HTTP requests from Keycloak’s network context. CVSS is 3.1: AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N.
Likely exposure
Exposure is limited to affected Red Hat Keycloak, JBoss EAP 8, EAP Expansion Pack, and Red Hat SSO 7 deployments using the vulnerable Keycloak services and the specific backchannel logout placeholder configuration. Internet-facing identity services may have higher practical monitoring priority.
Exploitation context
The CVE requires authentication and a non-default or specific client configuration. The source bundle does not indicate public exploit availability or active exploitation. CISA KEV status is false. The likely attacker goal is internal service discovery or limited information disclosure from the Keycloak server’s network location.
Researcher notes
Key constraints are important: authenticated attacker, high attack complexity, and the vulnerable placeholder-based backchannel logout configuration. Avoid assuming all Keycloak deployments are exploitable. Red Hat lists multiple affected product streams and advisories, with CVSS 3.1 and CWE-918.
Mitigation direction
Review Red Hat advisories RHSA-2026:25097, RHSA-2026:25098, RHSA-2026:30049, and RHSA-2026:30050.
Apply vendor-provided updates for affected Red Hat build of Keycloak, JBoss EAP, EAP XP, or SSO packages.
Confirm whether vulnerable clients use backchannel.logout.url with the application.session.host placeholder.
If updates are not yet possible, review vendor guidance and reduce risky backchannel logout configurations.
Restrict Keycloak outbound network access to only required destinations where operationally feasible.
Validation and detection
Inventory Keycloak and related Red Hat identity components against listed affected packages and versions.
Check client configurations for backchannel.logout.url containing the application.session.host placeholder.
Verify updated builds match Red Hat advisory guidance or listed unaffected builds where applicable.
Review Keycloak logs for unusual outbound request patterns during refresh token activity.
Confirm egress controls limit Keycloak access to internal APIs and metadata services.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.