# CVE-2026-117627: Keycloak-services: keycloak-services: jwt authorization grant bypasses identity provider login restrictions


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-4mr3-gfq4-fhxv

## What is CVE-2026-117627?

CVE-2026-117627 is a medium-severity vulnerability in Red Hat Build of Keycloak, published on 29 Oct 2026. 

### Official description

A flaw was found in the JWT Authorization Grant implementation of the keycloak-services component. When an OIDC or Google identity provider is configured with specific login restrictions, such as claim filtering, these checks are correctly applied during standard browser logins but are skipped during the JWT-based grant flow. This allows an authenticated client to obtain access tokens for a user even if their identity provider claims should have blocked the login.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-117627 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117627 is a medium-severity vulnerability in Red Hat Build of Keycloak, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117627 in the wild and no public exploit code.

Affected product: Red Hat Build of Keycloak. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-117627/ (Markdown: https://insights.sbomify.com/CVE-2026-117627/index.md)
```

## Sources

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

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