Vulnerability in golang-github-cli-go-gh-v2 (UBUNTU-CVE-2024-53859)

Summary

vulnerability in golang-github-cli-go-gh-v2 (UBUNTU-CVE-2024-53859). Confidential information can be exposed externally. Exploitable via ``GITHUB_TOKEN``. Mitigation: upgrade to `2.6.0-1ubuntu0.24.04.1~esm1` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **UBUNTU-CVE-2024-53859** has been found in golang-github-cli-go-gh-v2. Attackers can target a specific entry point like ``GITHUB_TOKEN`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: ?/10. What to do: upgrade golang-github-cli-go-gh-v2 to **2.6.0-1ubuntu0.24.04.1~esm1** or later. If unsure, ask your IT team or search "golang-github-cli-go-gh-v2 UBUNTU-CVE-2024-53859" on the vendor's site.

UBUNTU-CVE-2024-53859 (golang-github-cli-go-gh-v2) — Attack vector: local / unauthenticated Attack surface: `GITHUB_TOKEN` / `GH_TOKEN` / `GITHUB_ENTERPRISE_TOKEN` / `GH_ENTERPRISE_TOKEN` Patched: `2.6.0-1ubuntu0.24.04.1~esm1` — 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** (unclassified) exists in golang-github-cli-go-gh-v2. Attackers reach the vulnerable code path via ``GITHUB_TOKEN`` without authentication.

📍 Affected scope

golang-github-cli-go-gh-v2 — . Attack surface: `GITHUB_TOKEN` / `GH_TOKEN` / `GITHUB_ENTERPRISE_TOKEN` / `GH_ENTERPRISE_TOKEN`.

🔥 Severity

Severity: ?. Confidential information can be exposed externally

🔧 How to fix

Update to **2.6.0-1ubuntu0.24.04.1~esm1**.

🛡️ 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 request patterns matching this CVE's known IOCs. Run `grep -r 'golang-github-cli-go-gh-v2' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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

1
Identify exposure identify
```
grep -r 'golang-github-cli-go-gh-v2' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `golang-github-cli-go-gh-v2` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade golang-github-cli-go-gh-v2 to 2.6.0-1ubuntu0.24.04.1~esm1
```
ステージング環境で 2.6.0-1ubuntu0.24.04.1~esm1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:24.04:LTS golang-github-cli-go-gh-v2

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.0-1ubuntu0.24.04.1~esm1"}]}]

Ubuntu:25.10 golang-github-cli-go-gh-v2

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:26.04:LTS golang-github-cli-go-gh-v2