CVE-2026-97846 Red Hat CVE debrief

Who should care

Defenders responsible for Keycloak configurations and client credentials should assess exposure and verify token exchange configurations. They should review Keycloak configurations for potential vulnerabilities and prioritize verifying client credentials and token exchange configurations. Defenders must review Keycloak configurations for potential vulnerabilities and consider the potential operational impacts of token compromise.

Why it matters

A flaw in Keycloak's Standard Token Exchange V2 feature allows an attacker with stolen client credentials to obtain an unrestricted token, bypassing security protections. Defenders responsible for Keycloak configurations and client credentials should assess exposure and verify token exchange configurations.

• Potential token compromise requires verification of client credentials and token exchange configurations
• Defenders must review Keycloak configurations for potential vulnerabilities

Technical summary

The Standard Token Exchange V2 feature in Keycloak does not check for digital certificates, allowing an attacker with stolen client credentials to obtain an unrestricted token. This vulnerability affects Keycloak configurations and client credentials, potentially leading to token compromise. Defenders should assess exposure and verify token exchange configurations to mitigate potential risks. The vulnerability allows an attacker to bypass security protections, and further verification is required to determine the affected versions and remediation.

Defensive priority

Defenders should prioritize verifying client credentials and token exchange configurations.

Recommended defensive actions

• Verify client credentials and token exchange configurations
• Review Keycloak configurations for potential vulnerabilities
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability. Further verification is required to determine the affected versions and remediation. Defenders should verify client credentials and token exchange configurations to assess exposure. The vulnerability allows an attacker with stolen client credentials to obtain an unrestricted token, bypassing security protections. Evidence of affected product deployments and configurations is necessary to confirm exposure.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.