<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 10:23:58 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-236327</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-236327</link>
      <description>EUVD-2026-236327</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-236327</guid>
    </item>
    <item>
      <title>fkie_cve-2025-4143</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-4143</link>
      <description>&lt;p&gt;The OAuth implementation in workers-oauth-provider that is part of  MCP framework https://github.com/cloudflare/workers-mcp , did not correctly validate that redirect_uri was on the allowed list of redirect URIs for the given client registration.&lt;/p&gt;
&lt;p&gt;Fixed in:  https://github.com/cloudflare/workers-oauth-provider/pull/26 https://github.com/cloudflare/workers-oauth-provider/pull/26&lt;/p&gt;
&lt;p&gt;Impact:&lt;/p&gt;
&lt;p&gt;Under certain circumstances (see below), if a victim had previously authorized with a server built on workers-oath-provider, and an attacker could later trick the victim into visiting a malicious web site, then attacker could potentially steal the victim&amp;#39;s credentials to the same OAuth server and subsequently impersonate them.&lt;/p&gt;
&lt;p&gt;In order for the attack to be possible, the OAuth server&amp;#39;s authorized callback must be designed to auto-approve authorizations that appear to come from an OAuth client that the victim has authorized previously. The authorization flow is not implemented by workers-oauth-provider; it is up to the application built on top to decide whether to implement such automatic re-authorization. However, many applications do implement such logic.&lt;/p&gt;
&lt;p&gt;Note: It is a basic, well-known requirement that OAuth servers should verify that the redirect URI is among the allowed list for the client, both during the authorization flow and subsequently when exchanging the authorization code for an access token. workers-oauth-provider implemented only the latter check, not the former. Unfortuna…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The OAuth implementation in workers-oauth-provider that is part of  MCP framework https://github.com/cloudflare/workers-mcp , did not correctly validate that redirect_uri was on the allowed list of redirect URIs for the given client registration.&lt;/p&gt;
&lt;p&gt;Fixed in:  https://github.com/cloudflare/workers-oauth-provider/pull/26 https://github.com/cloudflare/workers-oauth-provider/pull/26&lt;/p&gt;
&lt;p&gt;Impact:&lt;/p&gt;
&lt;p&gt;Under certain circumstances (see below), if a victim had previously authorized with a server built on workers-oath-provider, and an attacker could later trick the victim into visiting a malicious web site, then attacker could potentially steal the victim&amp;#39;s credentials to the same OAuth server and subsequently impersonate them.&lt;/p&gt;
&lt;p&gt;In order for the attack to be possible, the OAuth server&amp;#39;s authorized callback must be designed to auto-approve authorizations that appear to come from an OAuth client that the victim has authorized previously. The authorization flow is not implemented by workers-oauth-provider; it is up to the application built on top to decide whether to implement such automatic re-authorization. However, many applications do implement such logic.&lt;/p&gt;
&lt;p&gt;Note: It is a basic, well-known requirement that OAuth servers should verify that the redirect URI is among the allowed list for the client, both during the authorization flow and subsequently when exchanging the authorization code for an access token. workers-oauth-provider implemented only the latter check, not the former. Unfortuna…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-4143</guid>
    </item>
    <item>
      <title>GHSA-4pc9-x2fx-p7vj — @cloudflare/workers-oauth-provider missing validation of redirect_uri on authorize endpoint</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4pc9-x2fx-p7vj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @cloudflare/workers-oauth-provider&lt;/p&gt;
&lt;p&gt;### Summary
The OAuth implementation failed to check that redirect_uri was among the allowed set for the client_id.&lt;/p&gt;
&lt;p&gt;### Impact
Under certain circumstances (see below), if a victim had previously authorized with a server built on workers-oath-provider, and an attacker could later trick the victim into visiting a malicious web site, then attacker could potentially steal the victim&amp;#39;s credentials to the same OAuth server and subsequently impersonate them.&lt;/p&gt;
&lt;p&gt;In order for the attack to be possible, the OAuth server&amp;#39;s authorized callback must be designed to auto-approve authorizations that appear to come from an OAuth client that the victim has authorized previously. The authorization flow is not implemented by workers-oauth-provider; it is up to the application built on top to decide whether to implement such automatic re-authorization. However, many applications do implement such logic.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in: https://github.com/cloudflare/workers-oauth-provider/pull/26&lt;/p&gt;
&lt;p&gt;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&amp;#39;ll need to update your MCP servers to use that version to resolve the vulnerability.&lt;/p&gt;
&lt;p&gt;### Workarounds
None&lt;/p&gt;
&lt;p&gt;### Note&lt;/p&gt;
&lt;p&gt;It is a basic, well-known requirement that OAuth servers should verify that the redirect URI is among the allowed list for the client, both during the authorization flow and subsequently when exchanging the authorization code for an…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @cloudflare/workers-oauth-provider&lt;/p&gt;
&lt;p&gt;### Summary
The OAuth implementation failed to check that redirect_uri was among the allowed set for the client_id.&lt;/p&gt;
&lt;p&gt;### Impact
Under certain circumstances (see below), if a victim had previously authorized with a server built on workers-oath-provider, and an attacker could later trick the victim into visiting a malicious web site, then attacker could potentially steal the victim&amp;#39;s credentials to the same OAuth server and subsequently impersonate them.&lt;/p&gt;
&lt;p&gt;In order for the attack to be possible, the OAuth server&amp;#39;s authorized callback must be designed to auto-approve authorizations that appear to come from an OAuth client that the victim has authorized previously. The authorization flow is not implemented by workers-oauth-provider; it is up to the application built on top to decide whether to implement such automatic re-authorization. However, many applications do implement such logic.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in: https://github.com/cloudflare/workers-oauth-provider/pull/26&lt;/p&gt;
&lt;p&gt;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&amp;#39;ll need to update your MCP servers to use that version to resolve the vulnerability.&lt;/p&gt;
&lt;p&gt;### Workarounds
None&lt;/p&gt;
&lt;p&gt;### Note&lt;/p&gt;
&lt;p&gt;It is a basic, well-known requirement that OAuth servers should verify that the redirect URI is among the allowed list for the client, both during the authorization flow and subsequently when exchanging the authorization code for an…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4pc9-x2fx-p7vj</guid>
    </item>
  </channel>
</rss>
