# CVE-2026-79652: Keycloak-services: keycloak-services: jwt bearer authorization grant does not enforce consentrequired

> An attacker with valid client credentials can bypass user consent requirements in the JWT Bearer grant to gain unauthorized access to user accounts.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Aug 2026
- **Updated:** 16 Sep 2026
- **Also known as:** CLEANSTART-2026-BB61412, GHSA-9f9p-c2v5-98rx

## What is CVE-2026-79652?

CVE-2026-79652 is a medium-severity missing authorization vulnerability in Red Hat Single Sign-On 7, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the JWT Bearer authorization grant implementation within the keycloak-services component of Red Hat Build of Keycloak. This component handles various OAuth2 and OpenID Connect grant types used for issuing access tokens. The issue occurs because the JWT Bearer grant fails to check if a client requires user consent before issuing a token. This allows an authenticated attacker with valid client credentials and a trusted identity provider assertion to bypass the consent requirement and obtain unauthorized access to a user account at a consent-gated client.

Weakness: CWE-862 (Missing Authorization)

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


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

Apply the vendor's patch.

## Is CVE-2026-79652 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79652 is a medium-severity missing authorization vulnerability in Red Hat Single Sign-On 7, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-79652 in the wild and no public exploit code.

Affected product: Red Hat Single Sign-On 7. 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-79652/ (Markdown: https://insights.sbomify.com/CVE-2026-79652/index.md)
```

## Sources

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

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