How severe is GHSA-xg9w-vg3g-6m68?

No CVSS score has been assigned to GHSA-xg9w-vg3g-6m68 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xg9w-vg3g-6m68?

GHSA-xg9w-vg3g-6m68 affects the following packages: guarddog (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-xg9w-vg3g-6m68?

Update guarddog to 2.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xg9w-vg3g-6m68 is resolved across your whole dependency graph.

How do I detect GHSA-xg9w-vg3g-6m68 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for guarddog. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-xg9w-vg3g-6m68 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.

How does O3 Security protect against GHSA-xg9w-vg3g-6m68?

O3 pinpoints whether GHSA-xg9w-vg3g-6m68 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-xg9w-vg3g-6m68 actively exploited in the wild?

No public exploit code has been indexed for GHSA-xg9w-vg3g-6m68 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-xg9w-vg3g-6m68?

GHSA-xg9w-vg3g-6m68 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 56th 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-xg9w-vg3g-6m68?

GHSA-xg9w-vg3g-6m68 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 GHSA-xg9w-vg3g-6m68 published, and has it been updated?

GHSA-xg9w-vg3g-6m68 was published on January 13, 2026 and was last updated on February 3, 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

GHSA-xg9w-vg3g-6m68

GuardDog Path Traversal Vulnerability Leads to Arbitrary File Overwrite and RCE

Also known asCVE-2026-22871

Published

Jan 13, 2026

Updated

Feb 3, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk56th percentile+0.71%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐍guarddog

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

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))  # ❌ VULNERABLE

Root 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 path parameter 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)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`guarddog`	all versions	2.7.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for guarddog. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update guarddog to 2.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xg9w-vg3g-6m68 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.
How O3 protects you
O3 pinpoints whether GHSA-xg9w-vg3g-6m68 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-xg9w-vg3g-6m68. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## 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` ```python elif zipfile.is_zipfile(source_archive): with zipfile.ZipFile(source_archive, "r") as zip: for file in zip.namelist():

O3 Security · Impact-Aware SCA

Is GHSA-xg9w-vg3g-6m68 in your dependencies?

O3 detects GHSA-xg9w-vg3g-6m68 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works