Keycloak-services: keycloak-services: client-level mandatory pkce bypass via login-actions entry point
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.24% · 15th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach10/20Shipped in major Linux distributions
- Severity7.8/10CVSS 6.8, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 85 if added to CISA KEV
- Would score about 80 if CISA's SSVC rates exploitation active
- Would score about 45 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- 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
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Write-ups · 1
Establishes: Technical detail and context.
- Report
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.