Vulnerability in org.keycloak:keycloak-services (CVE-2026-37979)
Summary
Vulnerability in org.keycloak:keycloak-services (CVE-2026-37979). Confidential information can be exposed externally. Mitigation: upgrade to 26.6.2 or later.
Original description
The description as published by the source.
A flaw was found in Keycloak. This access control vulnerability in Keycloak's OpenID Connect (OIDC) token introspection endpoint allows a confidential client to bypass audience restrictions. An attacker-controlled client with valid credentials can retrieve sensitive token claims intended for other resource servers, compromising the confidentiality of lightweight access tokens. This issue can be exploited remotely by any confidential client in the realm with valid credentials.
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-37979 has been found in org.keycloak:keycloak-services.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade org.keycloak:keycloak-services to 26.6.2 or later.
If unsure, ask your IT team or search "org.keycloak:keycloak-services CVE-2026-37979" on the vendor's site.
CVE-2026-37979 (org.keycloak:keycloak-services) — CWE-284 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 26.6.2 — 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.
A vulnerability (CWE-284) exists in org.keycloak:keycloak-services.
Check the vendor advisory for the affected versions of org.keycloak:keycloak-services.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 26.6.2.
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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.keycloak:keycloak-services を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.keycloak:keycloak-services to 26.6.2ステージング環境で 26.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory access.redhat.com
- advisory bugzilla.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- package github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com