Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-4874 low CVSS 3.1

SSRF (Server-Side Request Forgery) in org.keycloak:keycloak-services (CVE-2026-4874)

Summary

SSRF in org.keycloak:keycloak-services (CVE-2026-4874). Risk of unauthorized operations or information disclosure. Exploitable via ``client_session_host``. Mitigation: upgrade to `26.4.13` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-4874** has been found in org.keycloak:keycloak-services. Attackers can target a specific entry point like ``client_session_host`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10. What to do: upgrade org.keycloak:keycloak-services to **26.4.13** or later. If unsure, ask your IT team or search "org.keycloak:keycloak-services CVE-2026-4874" on the vendor's site.
CVE-2026-4874 (org.keycloak:keycloak-services) — CWE-918 / CVSS v3 3.1 Attack vector: remote (network-reachable) / no user interaction Attack surface: `client_session_host` / `backchannel.logout.url` / `application.session.host` Patched: `26.4.13` — apply immediately Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**SSRF** (CWE-918) exists in org.keycloak:keycloak-services. Attackers reach the vulnerable code path via ``client_session_host`` without authentication.
📍 Affected scope
org.keycloak:keycloak-services — . Attack surface: `client_session_host` / `backchannel.logout.url` / `application.session.host`.
🔥 Severity
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **26.4.13**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.keycloak:keycloak-services' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'org.keycloak:keycloak-services' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.keycloak:keycloak-services` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch 
    Upgrade org.keycloak:keycloak-services to 26.4.13

    ステージング環境で 26.4.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven org.keycloak:keycloak-services
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"26.4.13"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →