# CVE-2026-44971: GuardDog: Blind GitHub URL rewrite in remote project scanning causes SSRF and `GH_TOKEN` exfiltration

> Attackers can trigger SSRF and steal GitHub tokens by manipulating repository URLs during remote project scanning in GuardDog.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-587r-mc96-6f2p, PYSEC-2026-2505

## What is CVE-2026-44971?

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.

### Official 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 .

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-44971?

3 open source packages ship an affected version, including guarddog.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `guarddog` | PyPI | From 1.0.0 to 2.9.0 | None |
| `guarddog` | PyPI | From 1.0.0 to 2.9.0 | None |
| `guarddog` | PyPI | From 1.0.0 to 2.9.0 | None |

## How do I fix CVE-2026-44971?

No fix has been published for CVE-2026-44971 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44971 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44971 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44971 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44971 exists.

Affected packages and fixed versions:
- guarddog (PyPI): affected from 1.0.0 up to 2.9.0; no fix listed
- guarddog (PyPI): affected from 1.0.0 up to 2.9.0; no fix listed
- guarddog (PyPI): affected from 1.0.0 up to 2.9.0; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44971/ (Markdown: https://insights.sbomify.com/CVE-2026-44971/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44971
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44971
- OSV: https://osv.dev/vulnerability/CVE-2026-44971

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44971/
Summaries are generated and may contain mistakes; the official description above is the record.