GuardDog has a blind GitHub URL rewrite in remote project scanning causes SSRF and GH_TOKEN exfiltration

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

EPSS

• CVE-2026-44971: 0.24% estimated exploitation activity in the next 30 days; percentile 15.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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 GHTOKEN used by GuardDog. Description ProjectScanner.scanremote() takes a url, branch, and requirementsname, then constructs a raw GitHub URL by calling: Because this logic does not parse or validate the hostname, a crafted URL such as: is transformed into: Requests interprets this as an HTTP request to 127.0.0.1:18081, and GuardDog includes the configured GitHub credentials via HTTP Basic Auth. Reproduction summary 1. Start an HTTP listener on 127.0.0.1:18081 that logs the request path and Authorization header. 2. Set GITUSERNAME=alice and GHTOKEN=supersecret. 3. Call PypiRequirementsScanner().scanremote("http://github@127.0.0.1:18081/owner/repo", "main", "requirements.txt"). 4.…

Published by the source

11 May 2026, 14:45 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:45 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-587r-mc96-6f2p

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-587r-mc96-6f2p

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44971

Advisory: GuardDog has a blind GitHub URL rewrite in remote project scanning causes SSRF and `GH_TOKEN` exfiltration
IDs: CVE-2026-44971, GHSA-587r-mc96-6f2p
Record: https://patchnext.com/advisories/cve-2026-44971 (revision 2, source checked 26 Oct 2026, 13:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI guarddog: affected >= 1.0.0, <= 2.9.0

## Suggested inspection (read-only)
- `python -m pip show guarddog`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on guarddog.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-587r-mc96-6f2p (OSV record GHSA-587r-mc96-6f2p lists affected ranges: PyPI guarddog >=1.0.0 <=2.9.0)
- Verified: https://github.com/advisories/GHSA-587r-mc96-6f2p (GitHub-reviewed advisory GHSA-587r-mc96-6f2p lists affected ranges: PyPI guarddog >=1.0.0 <=2.9.0)

Commands are suggestions: review each one before running it.