# RFC 7636 violation - Weak enforcement of PKCE parameters in OAuth 2.0 implementation

**URL:** <https://community.auth0.com/t/rfc-7636-violation-weak-enforcement-of-pkce-parameters-in-oauth-2-0-implementation/187016>\
**Category:** Product Feedback\
**Tags:** security, pkce, code-verifier, authorization, auth0\
**Created:** [May 21, 2025, 12:46pm UTC](https://community.auth0.com/t/rfc-7636-violation-weak-enforcement-of-pkce-parameters-in-oauth-2-0-implementation/187016 "2025-05-21T12:46:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![manish.singh](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/manish.singh/32/72696_2.png) [@manish.singh](https://community.auth0.com/u/manish.singh)\
**Post date:** [May 21, 2025, 12:46pm UTC](https://community.auth0.com/t/rfc-7636-violation-weak-enforcement-of-pkce-parameters-in-oauth-2-0-implementation/187016/1 "2025-05-21T12:46:12Z")

</div>

**Feature:** Strict enforcement of PKCE parameters in OAuth 2.0 implementation

**Description:** PKCE ( Proof Key for Code Exchange) was introduced as an extension to OAuth 2.0 to mitigate risk of authorization code interception. We have observed that the application accepts authorization requests without code\_challenge and code\_challenge\_method but it still continues and issues an authorization code . However, during the token exchange, the server correctly enforces the presence and validity of the code\_verifier. This behavior of the application undermines PKCE’s two-step validation. This increases the applications susceptibility to error and misconfigurations or future attacks that exploit lax validation of PKCE parameters.

1. Click on “Sign in” to login into the application and intercept the request generated.
2. In the request, observe the code\_challenge and code\_challenge\_method parameter.
3. Remove the code\_challenge and code\_challenge\_method from the request and forward the request.
4. You will observe that the application proceeded successfully without giving any error and the user is logged in.

**Use-case:** PKCE authorization flow in OAuth 2.0

---

<div class="post-metadata">

**Author:** ![dawid.matuszczyk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dawid.matuszczyk/32/74550_2.png) [@dawid.matuszczyk](https://community.auth0.com/u/dawid.matuszczyk)\
**Post date:** [May 29, 2025, 1:14pm UTC](https://community.auth0.com/t/rfc-7636-violation-weak-enforcement-of-pkce-parameters-in-oauth-2-0-implementation/187016/2 "2025-05-29T13:14:57Z")

</div>

Hi there!

Welcome to the Auth0 Community!

Thank you for creating this feedback card. Please make sure to upvote it so that it gets as many votes as possible and attracts as many community members as possible.

Thanks  
Dawid

---

<div class="post-metadata">

**Author:** ![kmarek](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/kmarek/32/73201_2.png) [@kmarek](https://community.auth0.com/u/kmarek)\
**Post date:** [July 15, 2025, 8:54am UTC](https://community.auth0.com/t/rfc-7636-violation-weak-enforcement-of-pkce-parameters-in-oauth-2-0-implementation/187016/3 "2025-07-15T08:54:28Z")

</div>

I would also like to have it enforced. As of now it seems like the only way to enforce it is through a login action (described in another community post that I can not link here because links are disabled)
