Home

Description

A flaw was found in Keycloak. A remote attacker can exploit a Cross-Origin Resource Sharing (CORS) header injection vulnerability in Keycloak's User-Managed Access (UMA) token endpoint. This flaw occurs because the `azp` claim from a client-supplied JSON Web Token (JWT) is used to set the `Access-Control-Allow-Origin` header before the JWT signature is validated. When a specially crafted JWT with an attacker-controlled `azp` value is processed, this value is reflected as the CORS origin, even if the grant is later rejected. This can lead to the exposure of low-sensitivity information from authorization server error responses, weakening origin isolation, but only when a target client is misconfigured with `webOrigins: ["*"]`.

PUBLISHED Reserved 2026-04-06 | Published 2026-04-06 | Updated 2026-04-24 | Assigner redhat




LOW: 3.7CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Problem types

Origin Validation Error

Product status

Default status
affected

Timeline

2026-04-06:Reported to Red Hat.
2026-04-06:Made public.

References

access.redhat.com/security/cve/CVE-2026-37977 vdb-entry

bugzilla.redhat.com/show_bug.cgi?id=2455324 (RHBZ#2455324) issue-tracking

cve.org (CVE-2026-37977)

nvd.nist.gov (CVE-2026-37977)

Download JSON