CVE-2024-53858: Recursive repository cloning can leak authentication tokens to non-GitHub submodule hosts
Summary A security vulnerability has been identified in the GitHub CLI that could leak authentication tokens when cloning repositories containing git submodules hosted outside of GitHub.com and ghe.com. Details This vulnerability stems from several gh commands used to clone a repository with submodules from a non-GitHub host including gh repo clone, gh repo fork, gh pr checkout.
Published Nov 27, 2024 · Updated Dec 2, 2024
Affected packages
github.com/cli/cli/v2
- Ecosystem
- Go
- Affected
- <= 2.62.0
- Fixed in
- 2.63.0
- Check
go list -m github.com/cli/cli/v2
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A security vulnerability has been identified in the GitHub CLI that could leak authentication tokens when cloning repositories containing git submodules hosted outside of GitHub.com and ghe.com.
Details
This vulnerability stems from several gh commands used to clone a repository with submodules from a non-GitHub host including gh repo clone, gh repo fork, gh pr checkout. These GitHub CLI commands invoke git with instructions to retrieve authentication tokens using the `credential.helper` configuration variable for any host encountered.
Prior to 2.63.0, hosts other than GitHub.com and ghe.com are treated as GitHub Enterprise Server hosts and have tokens sourced from the following environment variables before falling back to host-specific tokens stored within system-specific secured storage:
GITHUB_ENTERPRISE_TOKENGH_ENTERPRISE_TOKENGITHUB_TOKEN_whenCODESPACESenvironment variable is set_
The result being git sending authentication tokens when cloning submodules.
In 2.63.0, these GitHub CLI commands will limit the hosts for which gh acts as a credential helper to source authentication tokens. Additionally, GITHUB_TOKEN will only be used for GitHub.com and ghe.com.
Impact
Successful exploitation could lead to a third-party using leaked authentication tokens to access privileged resources.
Remediation and mitigation
- Upgrade
ghto2.63.0 - Revoke authentication tokens used with the GitHub CLI:
- Personal access tokens
- GitHub CLI OAuth app
- Review your personal security log and any relevant audit logs for actions associated with your account or enterprise
Credited to BagToad, andyfeller, williammartin, jtmcg, Ry0taK.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-64652
GitHub CLI partially discloses authentication tokens in `gh auth status` output
low3.3Oct 15, 2026CVE-2026-64653
GitHub CLI allows path traversal through unescaped request URL components
low2.1Oct 15, 2026CVE-2026-64655
GitHub CLI allows attestation verification bypass through unescaped regex metacharacters
low2.1Oct 15, 2026CVE-2026-48501
GitHub CLI has an incorrect authorization header in API requests to TUF repository mirrors via `gh attestation`, `gh release verify`, and `gh release verify-asset` commands
high7.4May 29, 2026CVE-2026-45803
GitHub CLI: GitHub Actions log output in `gh run view` allows terminal escape sequence injection
low3.5No fixMay 19, 2026CVE-2025-25204
`gh attestation verify` returns incorrect exit code during verification if no attestations are present
medium6.3Feb 14, 2025
