# CVE-2026-97174: Keycloak CIBA parameter injection allows token spoofing

Source: https://junglewise.ai/threats/cve-2026-97174-a-flaw-was-found-in-the-client-initiated-backchannel  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-05. Updated: 2026-11-05  
License: CC BY 4.0 with a link back

CVE-2026-97174 · Severity: medium · CVSS 6.8 · Published 2026-11-05

Keycloak is an identity provider that issues security tokens for user authentication. A flaw in its backchannel authentication feature allows an attacker with legitimate credentials to receive security tokens for other users, gaining unauthorized access to their accounts. An attacker can log in as themselves but obtain tokens belonging to a victim, leading to full account takeover.

Technologies: [Red Hat Keycloak](https://junglewise.ai/threats/technologies/red-hat-keycloak). Vendors: [Red Hat](https://junglewise.ai/threats/vendors/red-hat).

## Quick answers

**Is CVE-2026-97174 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-97174 being exploited in the wild.

**How severe is CVE-2026-97174?** Medium severity, with a CVSS score of 6.8, published 5 November 2026.

**Which products and versions are affected?** Red Hat Keycloak.

**Is there a fix for CVE-2026-97174?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-97174 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-97174?** Check whether you run Red Hat Keycloak. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The Client-Initiated Backchannel Authentication (CIBA) endpoint fails to properly validate and isolate the subject (sub) parameter, allowing an attacker to inject it as an additional request parameter. During token issuance, this injected value overwrites the legitimate subject identifier in the serialized request. An authenticated attacker (Low privileges required) can exploit this over the network to obtain access and ID tokens for any user in the realm without user interaction.

## Affected products

- Red Hat Keycloak

## Timeline

- 2026-11-05: disclosed

## References

- [https://access.redhat.com/downloads/content/package-browser/](https://access.redhat.com/downloads/content/package-browser/)
- [https://access.redhat.com/security/cve/CVE-2026-97174](https://access.redhat.com/security/cve/CVE-2026-97174)

## Related threats

- [Red Hat Keycloak missing authorization check in group reparenting](https://junglewise.ai/threats/cve-2026-116468-a-flaw-was-found-in-the-group-move-and-organization-group)
- [Keycloak privilege escalation via client authentication manipulation](https://junglewise.ai/threats/cve-2026-9797-a-flaw-was-found-in-keycloak-s-administrative-services-org)
- [Keycloak Account REST API session manipulation](https://junglewise.ai/threats/cve-2026-97367-a-flaw-was-found-in-the-keycloak-account-rest-api-where-it)
- [Keycloak token exchange lifetime bypass in Standard Token Exchange V2](https://junglewise.ai/threats/cve-2026-96460-a-flaw-was-found-in-the-token-exchange-mechanism-of-keycloak-when)
- [Keycloak SAML broker ProxyRestriction bypass](https://junglewise.ai/threats/cve-2026-92856-a-flaw-was-found-in-the-saml-brokering-component-of-keycloak-an)