Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-9791 medium CVSS 4.3

Authorization Flaw in org.keycloak:keycloak-server-spi-private (CVE-2026-9791)

Summary

Vulnerability in org.keycloak:keycloak-server-spi-private (CVE-2026-9791). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

A flaw was found in Keycloak. An authenticated user with existing organization membership can exploit this flaw by accessing user-facing APIs, such as the account API or by requesting an OpenID Connect (OIDC) token with the 'organization' scope. This allows organization metadata to be disclosed in tokens, even after an administrator has explicitly disabled the Organizations feature, potentially leading to incorrect authorization decisions by resource servers.

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-9791 has been found in org.keycloak:keycloak-server-spi-private.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "org.keycloak:keycloak-server-spi-private CVE-2026-9791" on the vendor's site.

CVE-2026-9791 (org.keycloak:keycloak-server-spi-private) — CWE-863 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
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

Incorrect authorization (CWE-863) exists in org.keycloak:keycloak-server-spi-private.

📍 Affected scope

Check the vendor advisory for the affected versions of org.keycloak:keycloak-server-spi-private.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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-server-spi-private を使っているサービスとバージョンを洗い出す。

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

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

Affected packages

maven org.keycloak:keycloak-server-spi-private
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"26.4.7"}]}]
maven org.keycloak:keycloak-services
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"26.4.7"}]}]

References

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