Authorization Flaw in Keycloak (CVE-2026-11577)
Summary
Vulnerability in Keycloak (CVE-2026-11577). Successful exploitation can lead to full system takeover. Exploitable via POST /admin/realms/{realm}/partialImport.
Original description
The description as published by the source.
A flaw was found in Keycloak. A limited administrator can exploit an improper access control vulnerability in the POST /admin/realms/{realm}/partialImport endpoint. This allows them to bypass Fine-Grained Admin Permissions (FGAP) and escalate their privileges to a full realm administrator by importing users with realm-admin role mappings.
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-11577 has been found in Keycloak.
Attackers can target a specific entry point like POST /admin/realms/{realm}/partialImport over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Keycloak CVE-2026-11577" on the vendor's site.
CVE-2026-11577 (Keycloak) — CWE-863 / CVSS v3 7.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /admin/realms/{realm}/partialImport
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.
Incorrect authorization (CWE-863) exists in Keycloak. Attackers reach the vulnerable code path via POST /admin/realms/{realm}/partialImport.
Check the vendor advisory for the affected versions of Keycloak. Attack surface: POST /admin/realms/{realm}/partialImport.
Severity: High (CVSS 7.2/10). Successful exploitation can lead to full system takeover.
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 POST /admin/realms/{realm}/partialImport requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /admin/realms/{realm}/partialImport' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /admin/realms/{realm}/partialImportへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /admin/realms/{realm}/partialImport on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web access.redhat.com
- web bugzilla.redhat.com
- web github.com
- web nvd.nist.gov
- web github.com
- web security.access.redhat.com