We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Zendesk (Helpdesk and Chat)




wolfictl leaks GitHub tokens to remote non-GitHub git servers



wolfictl is a command line tool for working with Wolfi. A git authentication issue in versions prior to 0.16.10 allows a local user’s GitHub token to be sent to remote servers other than ``. 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. A central function `GetGitAuth` 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 `` library. Most callers (direct or indirect) of `GetGitAuth` use the token to authenticate to only; however, in some cases callers were passing this authentication without checking that the remote git repository was hosted on This behavior has existed in one form or another since commit 0d06e1578300327c212dda26a5ab31d09352b9d0 - committed January 25, 2023. 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 This also impacts anyone who ran `wolfictl update <url>` with a remote URL outside of Additionally, these subcommands must have run with the `GITHUB_TOKEN` environment variable set to a valid GitHub token. Users should upgrade to version 0.16.10 to receive a patch.


Problem types

CWE-552: Files or Directories Accessible to External Parties

CWE-668: Exposure of Resource to Wrong Sphere

Product status

< 0.16.10

References CVE-2024-35183 CVE-2024-35183

Download JSON

Share this page