<?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://vulnerability.circl.lu</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>Wed, 30 Sep 2026 01:53:51 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-67333</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-67333</link>
      <description>&lt;p&gt;better-auth before 1.6.13 (and pre-release builds 1.7.0-beta.0 through 1.7.0-beta.3) fail to validate the scheme of redirect_uris registered via the deprecated oidc-provider plugin and the mcp plugin (which wraps the same provider). An attacker can register an OAuth client with a javascript: redirect_uri, which the authorization server later returns unchanged in the consent response. If the deployment&amp;#39;s consent page navigates the browser to the returned redirectURI (e.g. assigning it to window.location.href), the attacker&amp;#39;s JavaScript executes in the authorization-server origin, exposing the victim&amp;#39;s session and enabling account takeover.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;better-auth before 1.6.13 (and pre-release builds 1.7.0-beta.0 through 1.7.0-beta.3) fail to validate the scheme of redirect_uris registered via the deprecated oidc-provider plugin and the mcp plugin (which wraps the same provider). An attacker can register an OAuth client with a javascript: redirect_uri, which the authorization server later returns unchanged in the consent response. If the deployment&amp;#39;s consent page navigates the browser to the returned redirectURI (e.g. assigning it to window.location.href), the attacker&amp;#39;s JavaScript executes in the authorization-server origin, exposing the victim&amp;#39;s session and enabling account takeover.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-67333</guid>
    </item>
    <item>
      <title>GHSA-w277-2xmj-j2rc</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-w277-2xmj-j2rc</link>
      <description>&lt;p&gt;better-auth before 1.6.13 (and pre-release builds 1.7.0-beta.0 through 1.7.0-beta.3) fail to validate the scheme of redirect_uris registered via the deprecated oidc-provider plugin and the mcp plugin (which wraps the same provider). An attacker can register an OAuth client with a javascript: redirect_uri, which the authorization server later returns unchanged in the consent response. If the deployment&amp;#39;s consent page navigates the browser to the returned redirectURI (e.g. assigning it to window.location.href), the attacker&amp;#39;s JavaScript executes in the authorization-server origin, exposing the victim&amp;#39;s session and enabling account takeover.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;better-auth before 1.6.13 (and pre-release builds 1.7.0-beta.0 through 1.7.0-beta.3) fail to validate the scheme of redirect_uris registered via the deprecated oidc-provider plugin and the mcp plugin (which wraps the same provider). An attacker can register an OAuth client with a javascript: redirect_uri, which the authorization server later returns unchanged in the consent response. If the deployment&amp;#39;s consent page navigates the browser to the returned redirectURI (e.g. assigning it to window.location.href), the attacker&amp;#39;s JavaScript executes in the authorization-server origin, exposing the victim&amp;#39;s session and enabling account takeover.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-w277-2xmj-j2rc</guid>
    </item>
  </channel>
</rss>
