Quick answers
- Is CVE-2026-96447 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96447 being exploited in the wild.
- How severe is CVE-2026-96447?
- Medium severity, with a CVSS score of 4.2, published 6 November 2026.
- Which products and versions are affected?
- Keycloak Keycloak.
- Is there a fix for CVE-2026-96447?
- 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-96447 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-96447?
- Check whether you run 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 TokenManager component in Keycloak improperly validates stateless access tokens when the original user ID no longer exists, falling back to username-based user resolution without verifying the token subject binding. An attacker with a valid stateless token from a deleted client can exploit this during client recreation to gain the identity and permissions of the replacement service account. This is a CWE-287 improper authentication vulnerability requiring network access and low privileges (a valid existing token).
Affected products
- Keycloak Keycloak
Timeline
- 2026-11-06: disclosed