Metrics
Affected Vendors & Products
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-gv94-wp4h-vv8p | Keycloak has Incorrect Behavior Order: Authorization Before Parsing and Canonicalization |
Solution
No solution given by the vendor.
Workaround
To mitigate this issue, configure any front-end security controls, such as Web Application Firewalls (WAFs) or reverse proxies, to strictly validate and normalize the `Authorization` header before forwarding requests to Keycloak. This ensures that only standard Bearer token formats are processed, preventing potential bypasses.
Thu, 08 Jan 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 08 Jan 2026 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Thu, 08 Jan 2026 04:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Keycloak: keycloak authorization header parsing leading to potential security control bypass | |
| First Time appeared |
Redhat
Redhat build Keycloak |
|
| Weaknesses | CWE-551 | |
| CPEs | cpe:/a:redhat:build_keycloak: | |
| Vendors & Products |
Redhat
Redhat build Keycloak |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-01-08T15:55:08.627Z
Reserved: 2026-01-08T02:52:15.720Z
Link: CVE-2026-0707
Updated: 2026-01-08T15:55:04.859Z
Status : Awaiting Analysis
Published: 2026-01-08T04:15:56.520
Modified: 2026-01-08T18:08:18.457
Link: CVE-2026-0707
OpenCVE Enrichment
No data.
Github GHSA