Quick answers
- Is CVE-2026-48099 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48099 being exploited in the wild.
- How severe is CVE-2026-48099?
- High severity, with a CVSS score of 7.1, published 13 August 2026.
- Which products and versions are affected?
- wsgidav (PyPI) <= 4.3.3, ECOSYSTEM:introduced=0,fixed=4.3.4.
- Is there a fix for CVE-2026-48099?
- Yes. wsgidav (PyPI): upgrade to 4.3.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48099 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-48099?
- Check whether you run wsgidav (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- wsgidav (PyPI): upgrade to 4.3.4 or later
pip install "wsgidav>=4.3.4"
Technical details
A path traversal vulnerability exists in WsgiDAV's `FilesystemProvider._loc_to_file_path()` method. The component uses `os.path.abspath` to resolve paths but validates containment using a simple string prefix check (`startswith`) which is not path-boundary aware. An attacker can use encoded dot segments (e.g., `%2e%2e`) to resolve to a sibling directory that happens to share the same prefix as the intended root (e.g., `/tmp/share` vs `/tmp/share_evil`). If the WSGI layer passes these segments through and the process has sufficient OS permissions, the attacker can perform GET, PUT, and DELETE operations on files outside the restricted root. The issue is fixed in version 4.3.4.
Affected products
- mar10 WsgiDAV <= 4.3.3
Identifiers
- CVE-2026-48099
- GHSA-wxq4-cc2q-338q
- PYSEC-2026-3428
Timeline
- 2026-05-27: disclosed
- 2026-06-11: advisory: GitHub Advisory published
- 2026-06-11: patched: Version 4.3.4 released