Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2026-64652

3.3 · LOW
Published Aug 6, 2026 CWE-201 EPSS 0.12% (2th pctl)

Overview

CVE-2026-64652 is a low-severity vulnerability. It was published on August 6, 2026 and has a CVSS 3.1 base score of 3.3 (LOW).

This vulnerability has a CVSS 3.1 base score of 3.3, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently Asked Questions

What is CVE-2026-64652?

CVE-2026-64652 is a low-severity vulnerability. It was published on August 6, 2026 and has a CVSS 3.1 base score of 3.3 (LOW).

How severe is CVE-2026-64652?

This vulnerability has a CVSS 3.1 base score of 3.3, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-64652?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64652?

CyberStrike's AI-powered security agents can automatically detect CVE-2026-64652 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.