# CVE-2026-0707: Keycloak: keycloak authorization header parsing leading to potential security control bypass

> Attackers can bypass security controls by exploiting overly permissive Bearer token header parsing in Keycloak.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-gv94-wp4h-vv8p

## What is CVE-2026-0707?

CVE-2026-0707 is a medium-severity vulnerability in Red Hat build of Keycloak 26.4, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-551 (Incorrect Behavior Order: Authorization Before Parsing and Canonicalization)

## Which versions are affected by CVE-2026-0707?

2 open source packages ship an affected version, including org.keycloak:keycloak-parent.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-parent` | Maven | All versions to 26.5.0 | None |
| `org.keycloak:keycloak-parent` | Maven | All versions to 26.5.0 | None |

## How do I fix CVE-2026-0707?

No fix has been published for CVE-2026-0707 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-0707 being exploited?

There is no known exploitation of CVE-2026-0707 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0707 and fix it if it is affected.

What it is: CVE-2026-0707 is a medium-severity vulnerability in Red Hat build of Keycloak 26.4, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0707 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-parent (Maven): affected all versions up to 26.5.0; no fix listed
- org.keycloak:keycloak-parent (Maven): affected all versions up to 26.5.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0707/ (Markdown: https://insights.sbomify.com/CVE-2026-0707/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0707
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0707
- OSV: https://osv.dev/vulnerability/CVE-2026-0707

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0707/
Summaries are generated and may contain mistakes; the official description above is the record.