Keycloak has Incorrect Behavior Order: Authorization Before Parsing and Canonicalization
A flaw was found in Keycloak. The Keycloak Authorization header parser is overly permissive regarding the formatting of the "Bearer" authentication scheme. It accepts non-standard characters (such as tabs) as separators and tolerates case variations that deviate from RFC 6750 specifications.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-0707US | — | — | ||
A flaw was found in Keycloak. The Keycloak Authorization header parser is overly permissive regarding the formatting of the "Bearer" authentication scheme. It accepts non-standard… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2026:3947WEB
- https://access.redhat.com/errata/RHSA-2026:3948WEB
- https://access.redhat.com/security/cve/CVE-2026-0707WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2427768WEB
- https://github.com/keycloak/keycloakPACKAGE
- https://github.com/keycloak/keycloak/issues/49433WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-0707ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan