GuarddogApplication · Datadoghq
CVE-2026-22871
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGuardDog is a CLI tool to identify malicious PyPI packages. Prior to 2.7.1, there is 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. This vulnerability is fixed in 2.7.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA path traversal vulnerability in GuardDog's safe_extract() function allows malicious PyPI packages to write files outside the intended extraction directory, potentially overwriting system files and achieving remote code execution on systems running the tool.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GuarddogApplication
< 2.7.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify GuardDog installationRun `pip show guarddog` or `pip list | grep -i guarddog` to confirm GuardDog is installed on the systemAffected if GuardDog is not installed on the system
-
Determine installed versionCheck the version displayed by `pip show guarddog` and compare it against the affected range: versions prior to 2.7.1 are vulnerableAffected if The installed version is lower than 2.7.1 (e.g., 2.7.0, 2.6.x, etc.)
-
Identify PyPI scanning usageReview GuardDog configuration files (e.g., guarddog-config.yaml, pyproject.toml, or config/ directory) for any PyPI package scanning settings or rulesAffected if PyPI package scanning is enabled in the GuardDog configuration
-
Check for recent PyPI package scansExamine GuardDog scan logs or command history for recent executions that scanned PyPI packages using the safe_extract() functionAffected if Logs or history show recent scanning of PyPI packages from untrusted sources
A system is affected if GuardDog version is below 2.7.1 and the tool is used to scan PyPI packages, as the vulnerable safe_extract() function handles the extraction.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.7.1
Upgrade GuardDog to version 2.7.1 or later to patch the path traversal vulnerability in safe_extract().
2.7.1
- Upgrade GuardDog to version 2.7.1 or later using your package manager (e.g., pip install guarddog==2.7.1 or pip install guarddog>=2.7.1)
- Verify the upgrade was successful by running guarddog --version to confirm the installed version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Guarddog
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22871 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22871 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data