CVE-2026-37977: Keycloak vulnerable to information disclosure via CORS header injection due to unvalidated JWT azp claim
(updated )
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: ["*"].
References
- access.redhat.com/errata/RHSA-2026:25097
- access.redhat.com/errata/RHSA-2026:25098
- access.redhat.com/errata/RHSA-2026:30049
- access.redhat.com/errata/RHSA-2026:30050
- access.redhat.com/security/cve/CVE-2026-37977
- bugzilla.redhat.com/show_bug.cgi?id=2455324
- github.com/advisories/GHSA-5v8v-xvjv-57x7
- github.com/keycloak/keycloak/commit/1439bd58a9f25b0d28d0400015f49f35f227ce04
- github.com/keycloak/keycloak/commit/461ce79a6cd6bfef7ca7fa41da287a3127f47ae4
- github.com/keycloak/keycloak/commit/ad34724a5d1ba8b6edf7a2c8c83826b1c20539e7
- github.com/keycloak/keycloak/issues/48036
- github.com/keycloak/keycloak/pull/49512
- nvd.nist.gov/vuln/detail/CVE-2026-37977
Code Behaviors & Features
Detect and mitigate CVE-2026-37977 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →