CVE-2025-4144: PKCE bypass via downgrade attack

Published May 1, 2025
·
Updated

Summary PKCE was implemented in the OAuth implementation in workers-oauth-provider that is part of MCP framework. However, it was found that an attacker could cause the check to be skipped.

Impact PKCE is a defense-in-depth mechanism against certain kinds of attacks and was an optional extension in OAuth 2.0 which became required in the OAuth 2.1 draft. (Note that the MCP specification requires OAuth 2.1.) This bug completely bypasses PKCE protection.

Patches Fixed in: https://github.com/cloudflare/workers-oauth-provider/pull/27

We patched up the vulnerabilities in the latest version, v 0.0.5 of the Workers OAuth provider (https://www.npmjs.com/package/@cloudflare/workers-oauth-provider). You'll need to update your MCP servers to use that version to resolve the vulnerability.

Workarounds None

Other sources

PKCE was implemented in the OAuth implementation in workers-oauth-provider that is part of MCP framework https://github.com/cloudflare/workers-mcp . However, it was found that an attacker could cause the check to be skipped.

Fixed in:

https://github.com/cloudflare/workers-oauth-provider/pull/27 https://github.com/cloudflare/workers-oauth-provider/pull/27

Impact:

PKCE is a defense-in-depth mechanism against certain kinds of attacks and was an optional extension in OAuth 2.0 which became required in the OAuth 2.1 draft. (Note that the MCP specification requires OAuth 2.1.). This bug completely bypasses PKCE protection.

MITRE

Affected Software

3 affected componentsFixes available
npm/@cloudflare/workers-oauth-provider<0.0.5
0.0.5
Cloudflare workers-oauth-provider=0.0.5
Cloudflare workers-oauth-provider

Event History

May 1, 2025
CVE Published
via MITRE·12:50 AM
Data Sourced
via MITRE·12:50 AM
DescriptionWeakness
Advisory Published
via GitHub·05:01 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-4144?

The severity of CVE-2025-4144 is considered to be high due to the potential for unauthorized access by skipping the PKCE checks.

2

How do I fix CVE-2025-4144?

To fix CVE-2025-4144, ensure you update the workers-oauth-provider to the latest version where the vulnerability has been patched.

3

What systems are affected by CVE-2025-4144?

CVE-2025-4144 affects the Cloudflare workers-oauth-provider as part of the MCP framework.

4

What attackers can do with CVE-2025-4144?

Attackers exploiting CVE-2025-4144 can bypass the PKCE validation, potentially gaining unauthorized access to resources.

5

Is CVE-2025-4144 related to OAuth security?

Yes, CVE-2025-4144 specifically involves a vulnerability in the OAuth implementation, affecting its security mechanism.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203