Skip to content

Enforce client level PKCE at the token endpoint - #55356

Draft
gaoyikeshuer wants to merge 1 commit into
keycloak:release/26.8from
gaoyikeshuer:backport-55116-26.8
Draft

gaoyikeshuer wants to merge 1 commit into
keycloak:release/26.8from
gaoyikeshuer:backport-55116-26.8

Conversation

@gaoyikeshuer

Copy link
Copy Markdown
Contributor

The token endpoint now runs the same PKCE parameter checks as the authorization endpoint against the challenge and method stored with the code, so a code issued without a challenge, or after the client's PKCE setting changed, is rejected.

Closes #55064

Co-authored-by: rmartinc rmartinc@redhat.com
Signed-off-by: Yike Gao yikegao8@gmail.com
(cherry picked from commit f2326fc)

The token endpoint now runs the same PKCE parameter checks as the authorization endpoint against the challenge and method stored with the code, so a code issued without a challenge, or after the client's PKCE setting changed, is rejected.

Closes keycloak#55064

Co-authored-by: rmartinc <rmartinc@redhat.com>
Signed-off-by: Yike Gao <yikegao8@gmail.com>
(cherry picked from commit f2326fc)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CVE-2026-125652] Client-level mandatory PKCE is not applied to authorization codes from the login-actions entry point

1 participant