# GuardDog: Unsanitized human-readable scan output allows terminal escape injection from malicious package content

Advisory record · `GHSA-m5p4-gvpx-4mvr`

- **Identifiers:** `GHSA-m5p4-gvpx-4mvr` · `CVE-2026-44972` · `PYSEC-2026-2506`
- **State:** Confirmed
- **Severity:** CVSS 5.0 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-116](https://cwe.mitre.org/data/definitions/116.html)
- **Tags:** [CWE-116](https://agentprime.io/advisories/tag/cwe-116.md)
- **Published:** 11 May 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 11 May 2026, 14:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `guarddog` (PyPI): affected `>=2.6.0, <=2.9.0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> GuardDog versions 2.6.0 through 2.9.0 do not escape terminal control characters in attacker-controlled values, such as file names, paths, messages, and code snippets, when printing the default human-readable scan output. A malicious package can exploit this by including terminal escape sequences in those values, which can clear or rewrite terminal output and spoof log content in CI when a user scans it. No fixed version is listed.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.0 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0011, the 1st percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:02 UTC: First seen by agentprime
- 31 Oct 2026, 15:02 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m5p4-gvpx-4mvr)

## Sources

- [GitHub Advisory Database: GHSA-m5p4-gvpx-4mvr](https://github.com/advisories/GHSA-m5p4-gvpx-4mvr)
- [OSV: GHSA-m5p4-gvpx-4mvr](https://osv.dev/vulnerability/GHSA-m5p4-gvpx-4mvr)
- <https://github.com/DataDog/guarddog/security/advisories/GHSA-m5p4-gvpx-4mvr>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-44972>
- <https://github.com/DataDog/guarddog>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-m5p4-gvpx-4mvr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m5p4-gvpx-4mvr/>. Everything for agents: <https://agentprime.io/llms.txt>.