CVE-2016-10075 is a high-severity (CVSS 7.8) CWE-17 vulnerability in tqdm. A fix is available for tqdm — see the affected versions and patch details below.
TDQM Arbitrary Code Execution
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
tqdm🐍tqdmReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
The tqdm._version module in tqdm versions 4.4.1 and 4.10 allows local users to execute arbitrary code via a crafted repo with a malicious git log in the current working directory.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | tqdm | ≥ 4.4.1&&< 4.11.2 | 4.11.2pip install --upgrade 'tqdm==4.11.2' |
| 🐍PyPI | tqdm | ≥ 4.10.0&&< 4.11.2 | 4.11.2pip install --upgrade 'tqdm==4.11.2' |
Affected Products
tqdmtqdm_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tqdm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tqdm to 4.11.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-10075 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2016-10075 in your dependencies?
Find it across PyPI, including transitive dependencies.