How severe is GHSA-g7vv-2v7x-gj9p?

GHSA-g7vv-2v7x-gj9p has a CVSS score of 3.9/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-g7vv-2v7x-gj9p?

GHSA-g7vv-2v7x-gj9p affects the following packages: tqdm (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-g7vv-2v7x-gj9p?

Update tqdm to 4.66.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g7vv-2v7x-gj9p is resolved across your whole dependency graph.

How do I detect GHSA-g7vv-2v7x-gj9p in my PyPI dependencies?

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.

How do I mitigate GHSA-g7vv-2v7x-gj9p if there is no patch (or I can't update yet)?

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.

Is GHSA-g7vv-2v7x-gj9p actively exploited in the wild?

No public exploit code has been indexed for GHSA-g7vv-2v7x-gj9p yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-g7vv-2v7x-gj9p?

GHSA-g7vv-2v7x-gj9p has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-g7vv-2v7x-gj9p?

GHSA-g7vv-2v7x-gj9p is classified as CWE-74 (CWE-74). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g7vv-2v7x-gj9p published, and has it been updated?

GHSA-g7vv-2v7x-gj9p was published on May 3, 2024 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

LOW severity

tqdm CLI arguments injection attackGHSA-g7vv-2v7x-gj9p

LOWFix: tqdm/tqdm@4e613f8

GHSA-g7vv-2v7x-gj9p is a low-severity (CVSS 3.9) CWE-74 vulnerability in tqdm. A fix is available for tqdm — see the affected versions and patch details below.

Also known asCVE-2024-34062PYSEC-2026-1976

Published

May 3, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-g7vv-2v7x-gj9p.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

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

1 pkg affected

🐍tqdm

Real-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

Impact

Any optional non-boolean CLI arguments (e.g. --delim, --buf-size, --manpath) are passed through python's eval, allowing arbitrary code execution. Example:

python -m tqdm --manpath="\" + str(exec(\"import os\nos.system('echo hi && killall python3')\")) + \""

Patches

https://github.com/tqdm/tqdm/commit/4e613f84ed2ae029559f539464df83fa91feb316 released in tqdm>=4.66.3

Workarounds

None

References

https://github.com/tqdm/tqdm/releases/tag/v4.66.3

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`tqdm`	≥ 4.4.0&&< 4.66.3	4.66.3`pip install --upgrade 'tqdm==4.66.3'`

Detection & mitigation playbook

Open-source dependency

Detect
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.66.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g7vv-2v7x-gj9p 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This flaw can only be triggered when python-tqdm is used directly via the command line with crafted arguments for non-boolean parameters such as `delim`, `buf-size`, and `manpath`. The rust-srpm-macros package as shipped by Red Hat Enterprise Linux 8 and 9 is not vulnerable to this issue because it does not use the…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-g7vv-2v7x-gj9p (CC BY 4.0)

Frequently Asked Questions

### Impact Any optional non-boolean CLI arguments (e.g. `--delim`, `--buf-size`, `--manpath`) are passed through python's `eval`, allowing arbitrary code execution. Example: ```sh python -m tqdm --manpath="\" + str(exec(\"import os\nos.system('echo hi && killall python3')\")) + \"" ``` ### Patches https://github.com/tqdm/tqdm/commit/4e613f84ed2ae029559f539464df83fa91feb316 released in `tqdm>=4.66.3` ### Workarounds None ### References - https://github.com/tqdm/tqdm/releases/tag/v4.66.3