<?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-06T20:08:03.620578+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/brew-datasette-cve-2025-64481</id>
    <title>BREW-datasette-CVE-2025-64481 — Open redirect endpoint in Datasette</title>
    <updated>2026-10-06T20:08:03.628296+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: datasette</p>
<p>Datasette is an open source multi-tool for exploring and publishing data. In versions 0.65.1 and below and 1.0a0 through 1.0a19, deployed instances of Datasette include an open redirect vulnerability. Hits to the path //example.com/foo/bar/ (the trailing slash is required) will redirect the user to https://example.com/foo/bar. This problem has been patched in both Datasette 0.65.2 and 1.0a21. To workaround this issue, if Datasette is running behind a proxy, that proxy could be configured to replace // with / in incoming request URLs.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-datasette-cve-2025-64481"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2025-64481</id>
    <title>CVE-2025-64481 — Open redirect endpoint in Datasette</title>
    <updated>2026-10-06T20:08:03.628363+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> simonw datasette</p>
<p>Datasette is an open source multi-tool for exploring and publishing data. In versions 0.65.1 and below and 1.0a0 through 1.0a19, deployed instances of Datasette include an open redirect vulnerability. Hits to the path //example.com/foo/bar/ (the trailing slash is required) will redirect the user to https://example.com/foo/bar. This problem has been patched in both Datasette 0.65.2 and 1.0a21. To workaround this issue, if Datasette is running behind a proxy, that proxy could be configured to replace // with / in incoming request URLs.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-64481"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-w832-gg5g-x44m</id>
    <title>GHSA-w832-gg5g-x44m — Open redirect endpoint in Datasette</title>
    <updated>2026-10-06T20:08:03.628407+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: datasette</p>
<p>### Impact</p>
<p>Deployed instances of Datasette prior to `0.65.2` and `1.0a21` include an open redirect vulnerability.</p>
<p>Hits to the path `//example.com/foo/bar/` (the trailing slash is required) will redirect the user to `https://example.com/foo/bar`.</p>
<p>### Patches</p>
<p>This problem has been patched in both Datasette `0.65.2` and `1.0a21`.</p>
<p>### Workarounds</p>
<p>If Datasette is running behind a proxy that proxy could be configured to replace `//` with `/` in incoming request URLs.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-w832-gg5g-x44m"/>
  </entry>
</feed>
