{"answers":{"affected":"3 open source packages ship an affected version, including guarddog.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44971 exists.","fix":"No fix has been published for CVE-2026-44971 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44971 is a high-severity server-side request forgery vulnerability in DataDog guarddog, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-44971 and fix it if it is affected.\n\nWhat it is: CVE-2026-44971 is a high-severity server-side request forgery vulnerability in DataDog guarddog, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44971 exists.\n\nAffected packages and fixed versions:\n- guarddog (PyPI): affected from 1.0.0 up to 2.9.0; no fix listed\n- guarddog (PyPI): affected from 1.0.0 up to 2.9.0; no fix listed\n- guarddog (PyPI): affected from 1.0.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-44971/ (Markdown: https://insights.sbomify.com/CVE-2026-44971/index.md)","id":"CVE-2026-44971","markdown":"https://insights.sbomify.com/CVE-2026-44971/index.md","name":"CVE-2026-44971","record":{"aliases":["GHSA-587r-mc96-6f2p","PYSEC-2026-2505"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python security scanner","requires_auth":"none","summary":"Attackers can trigger SSRF and steal GitHub tokens by manipulating repository URLs during remote project scanning in GuardDog.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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 .","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"GuardDog: Blind GitHub URL rewrite in remote project scanning causes SSRF and `GH_TOKEN` exfiltration","id":"CVE-2026-44971","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"GuardDog: Unsanitized human-readable scan output allows terminal escape injection from malicious package content","id":"CVE-2026-44972"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["1.0.0"],"last_affected":["2.9.0"],"package":"guarddog","purl":null,"source":"GHSA-587r-mc96-6f2p"},{"ecosystem":"PyPI","fixed":[],"introduced":["1.0.0"],"last_affected":["2.9.0"],"package":"guarddog","purl":"pkg:pypi/guarddog","source":"GHSA-587r-mc96-6f2p"},{"ecosystem":"PyPI","fixed":[],"introduced":["1.0.0"],"last_affected":["2.9.0"],"package":"guarddog","purl":"pkg:pypi/guarddog","source":"PYSEC-2026-2505"}],"prev":{"headline":"dbt MCP Server Transmits All MCP Tool Arguments Including Raw SQL and --vars Credentials to dbt Labs Telemetry by Default Without Redaction","id":"CVE-2026-44970"},"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-27","vendors":["DataDog"]},"summary":"Attackers can trigger SSRF and steal GitHub tokens by manipulating repository URLs during remote project scanning in GuardDog.","url":"https://insights.sbomify.com/CVE-2026-44971/"}