Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-64652

🟢 CVSS 3.3 — Low ✅ No Known Exploit CWE-201 NVD
3.3
CVSS Score
0 Low4 Medium7 High9 Critical10

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.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity none, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: Low — limited, and the attacker does not choose what is affected.
  • Integrity impact: None.
  • Availability impact: None.

Weakness class

CVE-2026-64652 is classified as CWE-201: Insertion of Sensitive Information Into Sent Data. The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

Affected software

CVE-2026-64652 is recorded against 1 package.

  • unknown

Timeline and source

Published on 6 August 2026 and last revised on 7 August 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

github.com
github.com
github.com

Other advisories for this package

unknown has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-201: Insertion of Sensitive Information Into Sent Data) in other software:

Details

Severity LOW
CVSS Score 3.3
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CWE CWE-201
Public Exploit ✅ No
Source NVD
Published 2026-08-06
Updated 2026-08-20
Modified 2026-08-07
Fix URL N/A

Affected Packages

Software From version Fixed in
unknown — —

Similar Threats

Free Vulnerability Check

Is your site affected by CVE-2026-64652?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2026-64652 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026
✓