CyberRota Analysis
AI-GeneratedGitHub CLI versions prior to 2.97.0 expose parts of fine-grained personal access tokens and GitHub App tokens when users execute the `gh auth status` command without the `--show-token` flag, potentially revealing sensitive information in terminal or CI outputs. The vulnerability primarily impacts authenticated users who utilize tokens containing underscores in their format, making it essential for these users to upgrade to version 2.97.0 to mitigate the risk of token exposure. Organizations relying on GitHub CLI for automation or CI/CD processes should prioritize this update to safeguard their access credentials.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
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.