# CVE-2026-125652: Keycloak-services: keycloak-services: client-level mandatory pkce bypass via login-actions entry point


- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-rp3r-7x6g-5mw6

## What is CVE-2026-125652?

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

### Official description

A flaw was found in the keycloak-services component of Keycloak, which provides the core authentication and authorization logic for the identity provider. The issue occurs when a user initiates a login after visiting the password reset page, causing the system to skip mandatory security checks for Proof Key for Code Exchange (PKCE). This could allow an attacker who intercepts a login code to gain unauthorized access to the user's account without needing the required security verifier.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-125652 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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