CVE-2026-44971
BaseFortify
Publication date: 2026-05-27
Last updated on: 2026-05-27
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| guarddog | guarddog | From 1.0.0 (inc) to 2.9.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in GuardDog, a CLI tool used to identify malicious PyPI packages. From versions 1.0.0 to 2.9.0, the tool rewrites attacker-controlled repository URLs using a blind string replacement method. When doing so, it sends the caller's GitHub credentials along with the request. This flaw allows an attacker who can influence the scanned repository URL to trigger a Server-Side Request Forgery (SSRF) attack and capture the GitHub token (GH_TOKEN) used by GuardDog.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to your GitHub credentials (GH_TOKEN) if an attacker can manipulate the repository URL being scanned. With the stolen token, an attacker could potentially access or manipulate your GitHub resources, leading to compromised code repositories, unauthorized actions, or data exposure.