Threats affecting pkg:pypi/guarddog

GuardDog is a CLI tool to identify malicious PyPI packages. From 1.0.0 to 2.9.0, the programmatic remote project scanning path rewrites attacker-controlled repository URLs using a blind string replacement and then sends the caller's GitHub credentials with the resulting request. This allows an attacker who can influence the scanned repository URL to trigger SSRF and capture the GH_TOKEN used by GuardDog. This vulnerability is fixed in .

GuardDog is a CLI tool to identify malicious PyPI packages. From 2.6.0 to 2.9.0, GuardDog includes attacker-controlled filenames, file locations, messages, and code snippets in its default human-readable output without escaping terminal control characters. A malicious package can therefore inject ANSI or OSC escape sequences into analyst terminals or CI logs.

CVE-2026-22871 is a high-severity path traversal vulnerability in DataDog's GuardDog CLI tool versions prior to 2.7.1. The flaw exists in the safe_extract() function, allowing malicious PyPI packages to write files outside the intended extraction directory. This arbitrary file overwrite can lead to remote code execution without requiring authentication, though user interaction is needed to trigger the extraction. The vulnerability has a CVSS 4.0 score of 8.7, indicating a significant risk. GuardDog is used to identify malicious PyPI packages, so compromised environments could be exploited by attackers to execute arbitrary code. The issue is fixed in version 2.

CVE-2026-22870 is a high-severity vulnerability in DataDog's GuardDog CLI tool versions prior to 2.7.1. The flaw arises from improper handling of highly compressed ZIP archives during extraction, specifically a lack of validation on decompressed file sizes. This allows attackers to craft malicious PyPI packages containing zip bombs that expand to consume gigabytes of disk space from a few megabytes of compressed data, leading to denial of service (DoS). Exploitation requires no privileges but does require user interaction to extract the malicious archive. The vulnerability impacts the availability of systems running vulnerable GuardDog versions. The issue has been fixed in version 2.7.1.