<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T10:35:15.544710+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-338140</id>
    <title>EUVD-2026-338140</title>
    <updated>2026-10-06T10:35:15.609943+00:00</updated>
    <content>EUVD-2026-338140</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-338140"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53513</id>
    <title>fkie_cve-2026-53513</title>
    <updated>2026-10-06T10:35:15.610007+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Better Auth is an authentication and authorization library for TypeScript. Prior to 1.6.11, the @better-auth/sso plugin's POST /sso/register and POST /sso/update-provider endpoints accept attacker-controlled oidcConfig.userInfoEndpoint, tokenEndpoint, and jwksEndpoint URLs when skipDiscovery: true is set, store them on the ssoProvider row without origin validation, and fetch them during OIDC callback, allowing non-blind server-side request forgery and possible account linking when trustEmailVerified: true is configured. This issue is fixed in version 1.6.11.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-53513"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-5rr4-8452-hf4v</id>
    <title>GHSA-5rr4-8452-hf4v — @better-auth/sso provider registration has server-side request forgery via unvalidated OIDC endpoints</title>
    <updated>2026-10-06T10:35:15.610117+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @better-auth/sso</p>
<p>### Am I affected?</p>
<p>Users are affected if all of the following are true:</p>
<p>- Their application uses `@better-auth/sso` at a version `&gt;= 0.1.0, &lt; 1.6.11` on the stable line, or any `1.7.0-beta.x` on the pre-release line.
- The `sso()` plugin is added to their application's `betterAuth({ plugins: [...] })` array.
- Any user with a valid Better Auth session can reach `POST /sso/register` (the plugin's default gate accepts any session).</p>
<p>For the non-blind SSRF impact (full IAM credential or internal HTTP body exfiltration), no further configuration is required.</p>
<p>For the account takeover escalation, additionally:</p>
<p>- Developers set `sso({ trustEmailVerified: true, ... })`.
- The developer's application deployment has accounts whose `email` overlaps with attacker-chosen domains.</p>
<p>If developers do not enable the SSO plugin, their application is not affected.</p>
<p>Fix:</p>
<p>1. Upgrade to `@better-auth/sso@1.6.11` or later.
2. If developers cannot upgrade, see workarounds below.</p>
<p>### Summary</p>
<p>The `@better-auth/sso` plugin's `POST /sso/register` endpoint accepts attacker-controlled `oidcConfig.userInfoEndpoint`, `tokenEndpoint`, and `jwksEndpoint` URLs when `skipDiscovery: true` is set, persists them on the `ssoProvider` row without origin validation, then issues server-side fetches to those URLs during the OIDC callback. The fetched response body is reflected through the user profile, producing a non-blind SSRF reachable by any authenticated session. The same primitive exists on `POST /sso/upd…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-5rr4-8452-hf4v"/>
  </entry>
</feed>
