CVE-2019-20916 is a relative path traversal vulnerability in pip before version 19.2 for Python. When pip processes a URL supplied to an install command, the download handling logic in _download_http_url within _internal/download.py uses the filename value from an HTTP Content-Disposition header without adequately neutralizing traversal sequences such as "../". A malicious server can therefore cause pip to write the downloaded content outside the intended destination directory by supplying a crafted filename in the response header. This can result in arbitrary file overwrite on the system running pip.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Arbitrary file read via path traversal in a Python package manager due to improper restriction of filenames in a Content-Disposition header.
A path traversal vulnerability in a Python package manager involving insufficient restriction of filenames in Content-Disposition headers, enabling arbitrary file read via ../ sequences.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.