<?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>Mon, 12 Oct 2026 06:35:03 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-207856</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-207856</link>
      <description>EUVD-2026-207856</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-207856</guid>
    </item>
    <item>
      <title>fkie_cve-2024-56734</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-56734</link>
      <description>&lt;p&gt;Better Auth is an authentication library for TypeScript. An open redirect vulnerability has been identified in the verify email endpoint of all versions of Better Auth prior to v1.1.6, potentially allowing attackers to redirect users to malicious websites. This issue affects users relying on email verification links generated by the library. The verify email callback endpoint accepts a `callbackURL` parameter. Unlike other verification methods, email verification only uses JWT to verify and redirect without proper validation of the target domain. The origin checker is bypassed in this scenario because it only checks for `POST` requests. An attacker can manipulate this parameter to redirect users to arbitrary URLs controlled by the attacker. Version 1.1.6 contains a patch for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Better Auth is an authentication library for TypeScript. An open redirect vulnerability has been identified in the verify email endpoint of all versions of Better Auth prior to v1.1.6, potentially allowing attackers to redirect users to malicious websites. This issue affects users relying on email verification links generated by the library. The verify email callback endpoint accepts a `callbackURL` parameter. Unlike other verification methods, email verification only uses JWT to verify and redirect without proper validation of the target domain. The origin checker is bypassed in this scenario because it only checks for `POST` requests. An attacker can manipulate this parameter to redirect users to arbitrary URLs controlled by the attacker. Version 1.1.6 contains a patch for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-56734</guid>
    </item>
    <item>
      <title>GHSA-8jhw-6pjj-8723 — Better Auth has an Open Redirect Vulnerability in Verify Email Endpoint</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8jhw-6pjj-8723</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: better-auth&lt;/p&gt;
&lt;p&gt;## Summary
An **open redirect vulnerability** has been identified in the **verify email endpoint** of Better Auth, potentially allowing attackers to redirect users to malicious websites. This issue affects users relying on email verification links generated by the library.&lt;/p&gt;
&lt;p&gt;## Affected Versions
- All versions prior to **v1.1.6**.&lt;/p&gt;
&lt;p&gt;## Impact
Attackers could craft malicious email verification links that exploit the redirect functionality to send users to untrusted domains. This can result in:&lt;/p&gt;
&lt;p&gt;- **Phishing attacks** – Users may unknowingly enter sensitive information on fake login pages.
- **Reputation damage** – Trust issues for applications using Better Auth.&lt;/p&gt;
&lt;p&gt;## Vulnerability Details
The verify email callback endpoint accepts a `callbackURL` parameter. Unlike other verification methods, email verification only uses JWT to verify and redirect without proper validation of the target domain. The origin checker is bypassed in this scenario because it only checks for `POST` requests. An attacker can manipulate this parameter to redirect users to arbitrary URLs controlled by the attacker.&lt;/p&gt;
&lt;p&gt;**Example Exploit:**
```
https://example.com/auth/verify-email?token=abcd1234&amp;amp;callbackURL=https://malicious-site.com
```&lt;/p&gt;
&lt;p&gt;## Patches
Upgrade to Better Auth **v1.1.6** or later. This version enforces domain validation for `callbackURL` for `/verify-email` path and for all other `GET` endpoints.&lt;/p&gt;
&lt;p&gt;## Workarounds
You can also use hooks to pre-check URLs in your auth instance to prevent this without…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: better-auth&lt;/p&gt;
&lt;p&gt;## Summary
An **open redirect vulnerability** has been identified in the **verify email endpoint** of Better Auth, potentially allowing attackers to redirect users to malicious websites. This issue affects users relying on email verification links generated by the library.&lt;/p&gt;
&lt;p&gt;## Affected Versions
- All versions prior to **v1.1.6**.&lt;/p&gt;
&lt;p&gt;## Impact
Attackers could craft malicious email verification links that exploit the redirect functionality to send users to untrusted domains. This can result in:&lt;/p&gt;
&lt;p&gt;- **Phishing attacks** – Users may unknowingly enter sensitive information on fake login pages.
- **Reputation damage** – Trust issues for applications using Better Auth.&lt;/p&gt;
&lt;p&gt;## Vulnerability Details
The verify email callback endpoint accepts a `callbackURL` parameter. Unlike other verification methods, email verification only uses JWT to verify and redirect without proper validation of the target domain. The origin checker is bypassed in this scenario because it only checks for `POST` requests. An attacker can manipulate this parameter to redirect users to arbitrary URLs controlled by the attacker.&lt;/p&gt;
&lt;p&gt;**Example Exploit:**
```
https://example.com/auth/verify-email?token=abcd1234&amp;amp;callbackURL=https://malicious-site.com
```&lt;/p&gt;
&lt;p&gt;## Patches
Upgrade to Better Auth **v1.1.6** or later. This version enforces domain validation for `callbackURL` for `/verify-email` path and for all other `GET` endpoints.&lt;/p&gt;
&lt;p&gt;## Workarounds
You can also use hooks to pre-check URLs in your auth instance to prevent this without…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8jhw-6pjj-8723</guid>
    </item>
  </channel>
</rss>
