CVE-2026-37977
A flaw was found in Keycloak. A remote attacker can exploit a …
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: ["*"]`.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- access.redhat.com/security/cve/CVE-2026-37977
- bugzilla.redhat.com/show_bug.cgi?id=2455324
- nvd.nist.gov/vuln/detail/CVE-2026-37977
- github.com/advisories/GHSA-5v8v-xvjv-57x7
- access.redhat.com/errata/RHSA-2026:25098
- access.redhat.com/errata/RHSA-2026:25097
- access.redhat.com/errata/RHSA-2026:30049
- access.redhat.com/errata/RHSA-2026:30050
- nvd.nist.gov/vuln/detail/CVE-2026-37977
- cve.org/CVERecord?id=CVE-2026-37977
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.