{"answers":{"affected":"3 open source packages ship an affected version, including guarddog.","exploited":"There is no known exploitation of CVE-2026-44972 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-44972 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44972 is a medium-severity vulnerability in DataDog guarddog, published on 27 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-44972 and fix it if it is affected.\n\nWhat it is: CVE-2026-44972 is a medium-severity vulnerability in DataDog guarddog, published on 27 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-44972 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- guarddog (PyPI): affected from 2.6.0 up to 2.9.0; no fix listed\n- guarddog (PyPI): affected from 2.6.0 up to 2.9.0; no fix listed\n- guarddog (PyPI): affected from 2.6.0 up to 2.9.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44972/ (Markdown: https://insights.sbomify.com/CVE-2026-44972/index.md)","id":"CVE-2026-44972","markdown":"https://insights.sbomify.com/CVE-2026-44972/index.md","name":"CVE-2026-44972","record":{"aliases":["GHSA-m5p4-gvpx-4mvr","PYSEC-2026-2506"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python security scanner","requires_auth":"none","summary":"Attackers can inject terminal escape sequences via malicious package content, potentially executing code or manipulating logs in analyst terminals.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"GuardDog: Unsanitized human-readable scan output allows terminal escape injection from malicious package content","id":"CVE-2026-44972","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"other","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Billy: Path traversal vulnerabilities","id":"CVE-2026-44973"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["2.6.0"],"last_affected":["2.9.0"],"package":"guarddog","purl":null,"source":"GHSA-m5p4-gvpx-4mvr"},{"ecosystem":"PyPI","fixed":[],"introduced":["2.6.0"],"last_affected":["2.9.0"],"package":"guarddog","purl":"pkg:pypi/guarddog","source":"GHSA-m5p4-gvpx-4mvr"},{"ecosystem":"PyPI","fixed":[],"introduced":["2.6.0"],"last_affected":["2.9.0"],"package":"guarddog","purl":"pkg:pypi/guarddog","source":"PYSEC-2026-2506"}],"prev":{"headline":"GuardDog: Blind GitHub URL rewrite in remote project scanning causes SSRF and `GH_TOKEN` exfiltration","id":"CVE-2026-44971"},"products":["guarddog"],"published":"2026-05-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-27","vendors":["DataDog"]},"summary":"Attackers can inject terminal escape sequences via malicious package content, potentially executing code or manipulating logs in analyst terminals.","url":"https://insights.sbomify.com/CVE-2026-44972/"}