Summary
internetarchive Vulnerable to Directory Traversal in File.download()
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
There is no direct workaround that does not involve upgrading the library. The vulnerability is in the core logic of the file download process.
The only alternative for users who absolutely cannot upgrade is to implement their own custom download function that:
- Manually sanitizes all filenames using a robust method.
- Validates that the resolved absolute path of the download target is within the intended directory before writing any files.
However, this essentially re-implements the fix and is not recommended. Upgrading to the patched version is the only safe and supported solution.
References
- Release Notes for v5.5.1
- Commit with the fix
- CVE Identifier: CVE-2025-58438
Impact
What kind of vulnerability is it?
This is a Critical severity directory traversal (path traversal) vulnerability in the File.download() method of the internetarchive library.
Who is impacted?
All users of the internetarchive library versions < 5.5.1 are impacted. The vulnerability is particularly critical for users on Windows systems, but all operating systems are affected.
Description of the vulnerability:
The vulnerability existed because the file.download() method did not properly sanitize user-supplied filenames or validate the final download path. A maliciously crafted filename could contain path traversal sequences (e.g., ../../../../windows/system32/file.txt) or illegal characters that, when processed, would cause the file to be written outside of the intended target directory.
Potential Impact:
An attacker could potentially overwrite critical system files or application configuration files, leading to a denial of service, privilege escalation, or remote code execution, depending on the context in which the library is used.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Has the problem been patched?
Yes, the problem has been patched.
What versions should users upgrade to?
Users must upgrade to version 5.5.1 or later.
Frequently Asked Questions
- What is CVE-2025-58438? CVE-2025-58438 is a critical-severity path traversal vulnerability in internetarchive (pip), affecting versions <= 5.5.0. It is fixed in 5.5.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of internetarchive are affected by CVE-2025-58438? internetarchive (pip) versions <= 5.5.0 is affected.
- Is there a fix for CVE-2025-58438? Yes. CVE-2025-58438 is fixed in 5.5.1. Upgrade to this version or later.
- Is CVE-2025-58438 exploitable, and should I be worried? Whether CVE-2025-58438 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-58438 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-58438? Upgrade
internetarchiveto 5.5.1 or later.