# CVE-2026-64652: GitHub CLI: Partial token disclosure in `gh auth status` output

> Authenticated users running gh auth status may inadvertently expose partial fine-grained or App tokens in terminal or CI logs due to insufficient masking.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** AZL-95468, DEBIAN-CVE-2026-64652, GHSA-cg6r-mpgc-h9mm, GO-2026-6766, MINI-gmw9-j774-4gxc, MINI-gx7f-9hp3-23ff, UBUNTU-CVE-2026-64652

## What is CVE-2026-64652?

CVE-2026-64652 is a low-severity vulnerability in cli, published on 6 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2026-64652?

4 open source packages ship an affected version, including github.com/cli/cli/v2 and github.com/cli/cli.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/cli/cli/v2` | Go | All versions | 2.97.0 |
| `github.com/cli/cli/v2` | Go | All versions | 2.97.0 |
| `github.com/cli/cli/v2` | Go | All versions | 2.97.0 |
| `github.com/cli/cli` | Go | All versions | None |

## How do I fix CVE-2026-64652?

Upgrade github.com/cli/cli/v2 to 2.97.0 or later.

## Is CVE-2026-64652 being exploited?

There is no known exploitation of CVE-2026-64652 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64652 and fix it if it is affected.

What it is: CVE-2026-64652 is a low-severity vulnerability in cli, published on 6 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64652 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/cli/cli/v2 (Go): affected all versions; fixed in 2.97.0
- github.com/cli/cli/v2 (Go): affected all versions; fixed in 2.97.0
- github.com/cli/cli/v2 (Go): affected all versions; fixed in 2.97.0
- github.com/cli/cli (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64652/ (Markdown: https://insights.sbomify.com/CVE-2026-64652/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64652
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64652
- OSV: https://osv.dev/vulnerability/CVE-2026-64652

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64652/
Summaries are generated and may contain mistakes; the official description above is the record.