Vulnerability in tqdm (CVE-2016-10075)
Summary
Vulnerability in tqdm (CVE-2016-10075). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.11.2 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2016-10075 has been found in tqdm.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade tqdm to 4.11.2 or later.
If unsure, ask your IT team or search "tqdm CVE-2016-10075" on the vendor's site.
CVE-2016-10075 (tqdm) — CWE-17 / CVSS v3 7.8
Attack vector: local / no user interaction
Patched: 4.11.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-17) exists in tqdm.
Check the vendor advisory for the affected versions of tqdm.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 4.11.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tqdm' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'tqdm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tqdmを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade tqdm to 4.11.2ステージング環境で 4.11.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2016-10075 tqdm Fixed in: 4.11.2-1
References
- advisory securityfocus.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web openwall.com
- web github.com
- web security.gentoo.org
- web github.com
- web github.com
- web web.archive.org