# CVE-2026-133226: A flaw was found in Keycloak.


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Nov 2026
- **Updated:** 20 Nov 2026
- **Also known as:** GHSA-qhf6-34gq-wxh5

## What is CVE-2026-133226?

CVE-2026-133226 is a medium-severity vulnerability in Red Hat Build of Keycloak, published on 20 Nov 2026. 

### Official description

A flaw was found in Keycloak. The Account API endpoint for sharing resources fails to verify whether owner-managed access is enabled and accepts permission scopes not assigned to the resource. An authenticated user can exploit this vulnerability to generate pre-granted permission tickets, causing Keycloak to bypass policy evaluation and issue access tokens with unauthorized scopes.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


Products: Redhat Build Keycloak.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:redhat:build_keycloak:*:*:*:*:*:*:*:*`

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Red Hat | red_hat_single_sign_on:7 | end of life | `rh-sso7-keycloak`, `rh-sso7-keycloak-server` |  |

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

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

## Is CVE-2026-133226 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-133226 is a medium-severity vulnerability in Red Hat Build of Keycloak, published on 20 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133226 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-133226/ (Markdown: https://insights.sbomify.com/CVE-2026-133226/index.md)
```

## Sources

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

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