<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T17:56:45.589148+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2025-66221</id>
    <title>CVE-2025-66221 — Werkzeug safe_join() allows Windows special device names</title>
    <updated>2026-10-01T17:56:45.591578+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> pallets werkzeug</p>
<p>Werkzeug is a comprehensive WSGI web application library. Prior to version 3.1.4, Werkzeug's safe_join function allows path segments with Windows device names. On Windows, there are special device names such as CON, AUX, etc that are implicitly present and readable in every directory. send_from_directory uses safe_join to safely serve files at user-specified paths under a directory. If the application is running on Windows, and the requested path ends with a special device name, the file will be opened successfully, but reading will hang indefinitely. This issue has been patched in version 3.1.4.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2025-66221"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-hgf8-39gv-g3f2</id>
    <title>GHSA-hgf8-39gv-g3f2 — Werkzeug safe_join() allows Windows special device names</title>
    <updated>2026-10-01T17:56:45.591669+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: werkzeug</p>
<p>Werkzeug's `safe_join` function allows path segments with Windows device names. On Windows, there are special device names such as `CON`, `AUX`, etc that are implicitly present and readable in every directory. `send_from_directory` uses `safe_join` to safely serve files at user-specified paths under a directory. If the application is running on Windows, and the requested path ends with a special device name, the file will be opened successfully, but reading will hang indefinitely.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-hgf8-39gv-g3f2"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/pysec-2026-2046</id>
    <title>PYSEC-2026-2046 — Werkzeug safe_join() allows Windows special device names</title>
    <updated>2026-10-01T17:56:45.591711+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: werkzeug</p>
<p>Werkzeug's `safe_join` function allows path segments with Windows device names. On Windows, there are special device names such as `CON`, `AUX`, etc that are implicitly present and readable in every directory. `send_from_directory` uses `safe_join` to safely serve files at user-specified paths under a directory. If the application is running on Windows, and the requested path ends with a special device name, the file will be opened successfully, but reading will hang indefinitely.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/pysec-2026-2046"/>
  </entry>
</feed>
