<?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-06T07:41:36.011468+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-341417</id>
    <title>EUVD-2026-341417</title>
    <updated>2026-10-06T07:41:36.014836+00:00</updated>
    <content>EUVD-2026-341417</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-341417"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-48370</id>
    <title>fkie_cve-2025-48370</title>
    <updated>2026-10-06T07:41:36.014872+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>auth-js is an isomorphic Javascript library for Supabase Auth. Prior to version 2.70.0, the library functions getUserById, deleteUser, updateUserById, listFactors and deleteFactor did not require the user supplied values to be valid UUIDs. This could lead to a URL path traversal, resulting in the wrong API function being called. Implementations that follow security best practice and validate user controlled inputs, such as the userId are not affected by this. This issue has been patched in version 2.70.0.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-48370"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-8r88-6cj9-9fh5</id>
    <title>GHSA-8r88-6cj9-9fh5 — auth-js Vulnerable to Insecure Path Routing from Malformed User Input</title>
    <updated>2026-10-06T07:41:36.014906+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @supabase/auth-js</p>
<p>### Impact
The library functions `getUserById`, `deleteUser`, `updateUserById`, `listFactors` and `deleteFactor` did not require the user supplied values to be valid UUIDs. This could lead to a URL path traversal, resulting in the wrong API function being called.</p>
<p>Implementations that follow security best practice and validate user controlled inputs, such as the `userId` are not affected by this.</p>
<p>### Patches
Strict value checks have been added to all affected functions. These functions now require that the `userId` and `factorId` parameters MUST be valid UUID (v4).</p>
<p>**Patched version:** &gt;= 2.69.1</p>
<p>### Workarounds
Implementations that follow security best practice and validate user controlled inputs, such as the `userId` are not affected by this. It is recommended that users of the auth-js library always follow security best practice and validate all inputs, before passing these to other functions or libraries.</p>
<p>### References
https://github.com/supabase/auth-js/pull/1063</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-8r88-6cj9-9fh5"/>
  </entry>
</feed>
