Live › vulnerability › CVE-2026-64652
Go to dashboardGitHub CLI's `gh auth status` masked only the part of certain tokens after the last underscore, so the start of a fine-grained PAT, GitHub App token, or Actions GITHUB_TOKEN could be printed. An attacker who can read that terminal output, CI log, or shared transcript gets part of a live token.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| github.com/cli/cli | go | all versions | – |
| github.com/cli/cli/v2 | go | < 2.97.0 | 2.97.0 |
Run gh --version and check whether it is below 2.97.0.
Find CI jobs or scripts that run gh auth status without --show-token and check whether their logs are visible to others.
2.97.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
GitHub CLI (gh) is GitHub's official command line tool. Prior to version 2.97.0, gh auth status masked only the characters after the last underscore in certain fine-grained personal access tokens and GitHub App tokens. As a result, part of an affected token could appear in terminal or CI output that is captured or shared. Authenticated users are affected if they ran gh auth status (without the --show-token flag) with a token type whose format contains an underscore after the prefix. This includes fine-grained personal access tokens (github_pat_) and GitHub App installation and user access tokens (ghs_, ghu_; for example, ghs_<APPID><JWT>), as well as the Actions GITHUB_TOKEN. Classic tokens such as gho and ghp_* have an underscore-free body and are not affected. This issue is fixed in version 2.97.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-64652")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.