CVE-2026-22871: GuardDog Path Traversal Vulnerability Leads to Arbitrary File Overwrite and RCE
Summary A path traversal vulnerability exists in GuardDog's safeextract() function that allows malicious PyPI packages to write arbitrary files outside the intended extraction directory, leading to Arbitrary File Overwrite and Remote Code Execution on systems running GuardDog.
Published Jan 13, 2026
Affected packages
guarddog
- Ecosystem
- PyPI
- Affected
- < 2.7.1
- Fixed in
- 2.7.1
- Check
pip show guarddog
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A path traversal vulnerability exists in GuardDog's safe_extract() function that allows malicious PyPI packages to write arbitrary files outside the intended extraction directory, leading to Arbitrary File Overwrite and Remote Code Execution on systems running GuardDog.
CWE: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)
Details
Vulnerable Code
File: guarddog/utils/archives.py
elif zipfile.is_zipfile(source_archive):
with zipfile.ZipFile(source_archive, "r") as zip:
for file in zip.namelist():
# Note: zip.extract cleans up any malicious file name
# such as directory traversal attempts This is not the
# case of zipfile.extractall
zip.extract(file, path=os.path.join(target_directory, file)) # ❌ VULNERABLERoot Cause
The comment about zip.extract() fooled me at first :) then I noticed the os.path.join() call. The vulnerability stems from incorrect usage of Python's `zipfile.ZipFile.extract()` API:
- The
pathparameter should be the target directory, not a full file path extract()automatically appends the member name to the path- By passing
os.path.join(target_directory, file), GuardDog causes the filename to be appended twice - This breaks zipfile's built-in path traversal sanitization
Attack Vector
- Attacker creates malicious wheel with path traversal filenames
- Uploads to PyPI or distributes directly
- Package scan:
guarddog pypi scan malicious-pkg - GuardDog downloads and extracts the package
- Malicious files written to arbitrary locations
- Code execution could be achieved
Impact
Impact depends on how GuardDog is running and under which environment.
Critical Scenarios
- Immediate Code Execution
- Write to
~/.bashrc→ executes on next shell - Write to
~/.profile→ executes on login
- Persistent Backdoors
- Write to
~/.ssh/authorized_keys→ SSH access - Write to
/etc/cron.d/malicious→ scheduled execution (if root) - Write to systemd user services → persistent execution
and more...
Credits
Reported by: Charbel (dwbruijn)
Credited to dwBruijn.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-44971
GuardDog has a blind GitHub URL rewrite in remote project scanning causes SSRF and `GH_TOKEN` exfiltration
high8.2No fixMay 11, 2026CVE-2026-44972
GuardDog: Unsanitized human-readable scan output allows terminal escape injection from malicious package content
medium5.0No fixMay 11, 2026CVE-2026-22870
GuardDog Zip Bomb Vulnerability in safe_extract() Allows DoS
high7.1Jan 13, 2026
