CVE-2026-22870
Datadoghq Guarddog ≤ 2.7.1
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-22870 is a high-severity Data Amplification (CWE-409) vulnerability in Datadoghq Guarddog. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SC-5 (Denial-of-service Protection) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-22870 is a denial-of-service vulnerability in GuardDog, a CLI tool designed to identify malicious PyPI packages. In versions prior to 2.7.1, the safe_extract() function does not validate decompressed file sizes when extracting ZIP archives, such as Python wheels and eggs. This flaw, classified under CWE-409 (Insufficient Resource Pool), allows attackers to craft zip bombs that expand a few megabytes of compressed data into gigabytes of disk space, exhausting storage resources. The vulnerability carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
Any attacker can exploit this vulnerability remotely by publishing a malicious PyPI package containing a zip bomb. Security practitioners or developers scanning untrusted packages with vulnerable GuardDog instances trigger the extraction process, leading to rapid disk space consumption and potential system denial of service. No user interaction, privileges, or special access is required, making it accessible over the network with low attack complexity.
The vulnerability is addressed in GuardDog version 2.7.1. Official mitigation details are available in the GitHub security advisory at https://github.com/DataDog/guarddog/security/advisories/GHSA-ffj4-jq7m-9g6v and the fixing commit at https://github.com/DataDog/guarddog/commit/c3fb07b4838945f42497e78b7a02bcfb1e63969b. Users should upgrade to 2.7.1 or later to prevent exploitation.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-2013
Vulnerability Data
GuardDog is a CLI tool to identify malicious PyPI packages. Prior to 2.7.1, GuardDog's safe_extract() function does not validate decompressed file sizes when extracting ZIP archives (wheels, eggs), allowing attackers to cause denial of service through zip bombs. A malicious…
more
package can consume gigabytes of disk space from a few megabytes of compressed data. This vulnerability is fixed in 2.7.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation can reject or limit decompression of data whose expansion ratio exceeds safe thresholds.
DoS protection limits the resource-exhaustion impact when a decompression bomb is processed.
Resource allocation controls bound memory/CPU consumption that a data-amplification attack would otherwise exhaust.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices include input-validation and resource-limit checks that prevent improper handling of compressed data.
Runtime monitoring of compute resources can detect exhaustion caused by decompression bombs.
Capacity planning and monitoring directly limits the availability impact of data-amplification attacks.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can uncover decompression-bomb vulnerabilities before release.
Redundancy helps availability but does not address the root cause of the weakness.
Monitoring can detect anomalous resource usage but does not prevent the weakness.
Secure development lifecycle includes input validation and resource-limit checks that mitigate data-amplification attacks.
Application security requirements can mandate limits on decompression size and ratio.
Secure architecture principles encourage defensive design against resource-exhaustion threats.