Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-64652 low CVSS 3.3

Vulnerability in github.com/cli/cli/v2 (CVE-2026-64652)

Summary

Vulnerability in github.com/cli/cli/v2 (CVE-2026-64652). Risk of unauthorized operations or information disclosure. Exploitable via DELETE /installation/token. Mitigation: upgrade to 2.97.0 or later.

Original description

The description as published by the source.

Summary

A security vulnerability has been identified in GitHub CLI where gh auth status could potentially print a portion of the authentication token in plaintext, depending on the lexical structure of the token.

Affected users:

  • Authenticated users who 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/user access tokens (ghs_*, ghu_*, e.g., ghs__), including the Actions GITHUB_TOKEN. Classic tokens such as gho_* and ghp_* have an underscore-free body and are not affected.

Details

The vulnerability stems from the way GitHub CLI masks the authentication token when reporting authentication state:

  1. A user runs gh auth status without --show-token, expecting the token to be fully masked.
  2. The masking logic redacts only the characters that follow the last underscore in the token, instead of redacting everything after the token prefix.
  3. The partially masked token is written to the command output, where it can be captured or shared.

Because gh auth status is a diagnostic command commonly run interactively and inside automated environments, the leaked token characters can end up in CI/CD job logs, terminal scrollback, screen recordings, screenshots, or pasted output shared in bug reports and support requests.

In v2.97.0, GitHub CLI fully masks the token in gh auth status…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-64652 has been found in github.com/cli/cli/v2.
Attackers can target a specific entry point like DELETE /installation/token over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: upgrade github.com/cli/cli/v2 to 2.97.0 or later.
If unsure, ask your IT team or search "github.com/cli/cli/v2 CVE-2026-64652" on the vendor's site.

CVE-2026-64652 (github.com/cli/cli/v2) — CWE-201 / CVSS v3 3.3
Attack vector: local / no user interaction
Attack surface: DELETE /installation/token / GITHUB_TOKEN
Patched: 2.97.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-201) exists in github.com/cli/cli/v2. Attackers reach the vulnerable code path via DELETE /installation/token.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/cli/cli/v2. Attack surface: DELETE /installation/token / GITHUB_TOKEN.

🔥 Severity

Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.97.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual DELETE /installation/token requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/cli/cli/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/cli/cli/v2' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/cli/cli/v2 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'DELETE /installation/token' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで DELETE /installation/token への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/cli/cli/v2 to 2.97.0

    ステージング環境で 2.97.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against DELETE /installation/token on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/cli/cli/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.97.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details