<?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-15T05:32:05.363422+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-352524</id>
    <title>EUVD-2026-352524</title>
    <updated>2026-10-15T05:32:05.365964+00:00</updated>
    <content>EUVD-2026-352524</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-352524"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-48099</id>
    <title>fkie_cve-2026-48099</title>
    <updated>2026-10-15T05:32:05.365994+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>WsgiDAV is a generic and extendable WebDAV server based on WSGI. WsgiDAV 4.3.3 and prior can allow a WebDAV request path containing an encoded parent-directory segment to escape the configured filesystem share root in a specific path layout. The issue is fixed with version 4.3.4.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-48099"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-wxq4-cc2q-338q</id>
    <title>GHSA-wxq4-cc2q-338q — WsgiDAV encoded dot segments can escape filesystem share roots</title>
    <updated>2026-10-15T05:32:05.366024+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: wsgidav</p>
<p>### Impact
WsgiDAV 4.3.3 can allow a WebDAV request path containing an encoded parent-directory segment to escape the configured filesystem share root in a specific path layout.</p>
<p>### Patches
The issue is fixed with version 4.3.4.</p>
<p>### Preconditions</p>
<p>The practical impact depends on the deployment.</p>
<p>The deployment uses a filesystem-backed WsgiDAV share.</p>
<p>The attacker can send WebDAV requests accepted by that share. This may be an anonymous share or an authenticated WebDAV user. This is not an authentication bypass.</p>
<p>### Details</p>
<p>The issue is in `FilesystemProvider._loc_to_file_path()`. The method builds a candidate path with `os.path.abspath(os.path.join(root_path, *path_parts))`, then checks containment with `file_path.startswith(root_path)`. This is not path-boundary aware. For example, if the configured share root is `/tmp/share`, a resolved sibling path such as `/tmp/share_evil/secret.txt` still starts with the string `/tmp/share`.</p>
<p>In a local proof, this allowed GET, PUT, and DELETE requests to operate on files outside the configured share root.</p>
<p>The WSGI/server layer forwards the encoded dot segment to WsgiDAV's PATH_INFO. The local proof used `/%2e%2e/...`, which wsgiref passed through as `/../...`.</p>
<p>A sibling or neighboring path exists whose absolute path starts with the configured root path string, such as `/tmp/share` and `/tmp/share_evil`.</p>
<p>The WsgiDAV process has OS permissions for the outside path.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-wxq4-cc2q-338q"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-3428</id>
    <title>PYSEC-2026-3428 — WsgiDAV encoded dot segments can escape filesystem share roots</title>
    <updated>2026-10-15T05:32:05.366063+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: wsgidav</p>
<p>### Impact
WsgiDAV 4.3.3 can allow a WebDAV request path containing an encoded parent-directory segment to escape the configured filesystem share root in a specific path layout.</p>
<p>### Patches
The issue is fixed with version 4.3.4.</p>
<p>### Preconditions</p>
<p>The practical impact depends on the deployment.</p>
<p>The deployment uses a filesystem-backed WsgiDAV share.</p>
<p>The attacker can send WebDAV requests accepted by that share. This may be an anonymous share or an authenticated WebDAV user. This is not an authentication bypass.</p>
<p>### Details</p>
<p>The issue is in `FilesystemProvider._loc_to_file_path()`. The method builds a candidate path with `os.path.abspath(os.path.join(root_path, *path_parts))`, then checks containment with `file_path.startswith(root_path)`. This is not path-boundary aware. For example, if the configured share root is `/tmp/share`, a resolved sibling path such as `/tmp/share_evil/secret.txt` still starts with the string `/tmp/share`.</p>
<p>In a local proof, this allowed GET, PUT, and DELETE requests to operate on files outside the configured share root.</p>
<p>The WSGI/server layer forwards the encoded dot segment to WsgiDAV's PATH_INFO. The local proof used `/%2e%2e/...`, which wsgiref passed through as `/../...`.</p>
<p>A sibling or neighboring path exists whose absolute path starts with the configured root path string, such as `/tmp/share` and `/tmp/share_evil`.</p>
<p>The WsgiDAV process has OS permissions for the outside path.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-3428"/>
  </entry>
</feed>
