# CVE-2026-19688: Keycloak Admin REST API audience verification bypass

Source: https://junglewise.ai/threats/cve-2026-19688-a-flaw-was-found-in-the-admin-rest-api-of-keycloak-an-identity  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-06. Updated: 2026-11-06  
License: CC BY 4.0 with a link back

CVE-2026-19688 · Severity: medium · CVSS 6.8 · Published 2026-11-06

Keycloak is an identity and access management platform used to control who can access corporate applications and resources. A flaw in its Admin REST API allows an attacker who controls an application within Keycloak to steal an administrator's authentication token and reuse it to take over the entire system, including modifying users, changing permissions, and compromising all protected applications.

Technologies: [Keycloak](https://junglewise.ai/threats/technologies/keycloak). Vendors: [Keycloak](https://junglewise.ai/threats/vendors/keycloak).

## Quick answers

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

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

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

**Is there a fix for CVE-2026-19688?** 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-19688 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-19688?** 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 Admin REST API fails to verify the audience (intended recipient) of JWT bearer tokens during authentication, allowing token reuse across different security contexts. An attacker operating a client application within a Keycloak realm can capture an administrator's access token and replay it to perform unauthorized administrative operations. This is an improper authentication weakness (CWE-287) that requires the attacker to first compromise or control a client and for an admin to authenticate through it.

## Affected products

- Keycloak Keycloak

## Timeline

- 2026-11-06: 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-19688](https://access.redhat.com/security/cve/CVE-2026-19688)

## Related threats

- [Keycloak login-failure storage synchronization error in MySQL/MariaDB](https://junglewise.ai/threats/cve-2026-112201-a-flaw-was-found-in-the-login-failure-storage-component-of)
- [Keycloak PKCE bypass in login after password reset](https://junglewise.ai/threats/cve-2026-125652-a-flaw-was-found-in-the-keycloak-services-component-of-keycloak)
- [Keycloak server arbitrary code execution in client authorization](https://junglewise.ai/threats/cve-2026-120984-a-flaw-was-found-in-the-keycloak-server-s-client-management)
- [Keycloak token sanitization bypass in protocol mapper](https://junglewise.ai/threats/cve-2026-97848-a-flaw-was-found-in-the-token-sanitization-logic-of-keycloak-an)
- [Keycloak Dynamic Client Registration privilege escalation](https://junglewise.ai/threats/cve-2026-96547-a-flaw-was-found-in-the-dynamic-client-registration-component-of)