Information Exposure Affecting gh package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.12% (2nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-GH-18674513
  • published12 Aug 2026
  • disclosed6 Aug 2026

Introduced: 6 Aug 2026

NewCVE-2026-64652  (opens in a new tab)
CWE-201  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest gh.

NVD Description

Note: Versions mentioned in the description apply only to the upstream gh package and not the gh package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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.