Cross-Site Scripting (XSS) in Keycloak (CVE-2026-37980)
Summary
Cross-site scripting in Keycloak (CVE-2026-37980). Confidential information can be exposed externally. Exploitable via organization.alias.
Original description
The description as published by the source.
A flaw was found in Keycloak, specifically in the organization selection login page. A remote attacker with manage-realm or manage-organizations administrative privileges can exploit a Stored Cross-Site Scripting (XSS) vulnerability. This flaw occurs because the organization.alias is placed into an inline JavaScript onclick handler, allowing a crafted JavaScript payload to execute in a user's browser when they view the login page. Successful exploitation enables arbitrary JavaScript execution, potentially leading to session theft, unauthorized account actions, or further attacks against users of the affected realm.
Source: NIST National Vulnerability Database NVD
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-37980 has been found in Keycloak.
Attackers can target a specific entry point like organization.alias over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Keycloak CVE-2026-37980" on the vendor's site.
CVE-2026-37980 (Keycloak) — CWE-79 / CVSS v3 6.9
Attack vector: remote (network-reachable)
Attack surface: organization.alias / onclick
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.
Cross-site scripting (XSS) (CWE-79) exists in Keycloak. Attackers reach the vulnerable code path via organization.alias.
Check the vendor advisory for the affected versions of Keycloak. Attack surface: organization.alias / onclick.
Severity: Medium (CVSS 6.9/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Keycloak' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Keycloak' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Keycloakを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch secalert@redhat.com
- patch secalert@redhat.com