Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-9087 medium CVSS 6.4

Vulnerability in org.keycloak:keycloak-services (CVE-2026-9087)

Summary

Vulnerability in org.keycloak:keycloak-services (CVE-2026-9087). Confidential information can be exposed externally. Mitigation: upgrade to 26.6.3 or later.

Original description

The description as published by the source.

A flaw was found in Keycloak. The cross-session verification proof is keyed only by (local userId,
idpAlias) and is not bound to the upstream identity that was actually verified, so a second upstream account on the same IdP can consume it and get linked to the victim's local account.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-9087 has been found in org.keycloak:keycloak-services.
Confidential information can be exposed externally. CVSS score: 6.4/10.
What to do: upgrade org.keycloak:keycloak-services to 26.6.3 or later.
If unsure, ask your IT team or search "org.keycloak:keycloak-services CVE-2026-9087" on the vendor's site.

CVE-2026-9087 (org.keycloak:keycloak-services) — CWE-639 / CVSS v3 6.4
Attack vector: remote (network-reachable)
Patched: 26.6.3 — 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

A vulnerability (CWE-639) exists in org.keycloak:keycloak-services.

📍 Affected scope

Check the vendor advisory for the affected versions of org.keycloak:keycloak-services.

🔥 Severity

Severity: Medium (CVSS 6.4/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 26.6.3.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.keycloak:keycloak-services を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.keycloak:keycloak-services to 26.6.3

    ステージング環境で 26.6.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

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

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details