How severe is CVE-2004-1444?

No CVSS score has been assigned to CVE-2004-1444 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2004-1444?

CVE-2004-1444 affects the following packages: roundup (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2004-1444?

Update roundup to 0.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2004-1444 is resolved across your whole dependency graph.

How do I detect CVE-2004-1444 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for roundup, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2004-1444 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2004-1444 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2004-1444, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2004-1444?

CVE-2004-1444 has an EPSS (Exploit Prediction Scoring System) score of 8.9%, placing it in the 95th 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 CVE-2004-1444?

CVE-2004-1444 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2004-1444 published, and has it been updated?

CVE-2004-1444 was published on April 29, 2022 and was last updated on July 6, 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

CVE-2004-1444 — roundup

CVE-2004-1444 is a Path Traversal vulnerability in roundup. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for roundup — see the affected versions and patch details below.

Roundup Directory traversal vulnerability

Also known asPYSEC-2026-745

Published

Apr 29, 2022

Updated

Jul 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

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

EPSS Exploitation Probability

via FIRST.org ↗

8.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍roundup

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

Directory traversal vulnerability in Roundup 0.6.4 and earlier allows remote attackers to view arbitrary files via .. (dot dot) sequences in an @@ command in an HTTP GET request.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`roundup`	all versions	0.7.3`pip install --upgrade 'roundup==0.7.3'`

Affected Products

1 product · 46 configurations

Application

rounduproundup-tracker

≤ 0.6.4

32 versions

0.1.00.1.10.1.20.1.30.2.00.2.10.2.20.2.30.2.40.2.50.2.60.2.7

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-24179remotelinux✓ Verified

Roundup 0.5/0.6 - Remote File Disclosure

by Vickenty Fesunov · Jun 8, 2004

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for roundup, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update roundup to 0.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2004-1444 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Directory traversal vulnerability in Roundup 0.6.4 and earlier allows remote attackers to view arbitrary files via `..` (dot dot) sequences in an `@@` command in an HTTP GET request.