Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-45803 low CVSS 3.5

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

Summary

Vulnerability in github.com/cli/cli/v2 (CVE-2026-45803). Risk of unauthorized operations or information disclosure. Exploitable via screen. Mitigation: upgrade to 2.92.0 or later.

Original description

The description as published by the source.

Summary

A security vulnerability has been identified in GitHub CLI that could allow terminal escape sequence injection when users view GitHub Actions workflow logs using gh run view --log or gh run view --log-failed.

Details

The vulnerability stems from the way GitHub CLI handles raw Actions log output. The gh run view --log and gh run view --log-failed commands stream workflow log lines to stdout or the configured pager without sanitizing terminal control sequences. An attacker who can influence GitHub Actions log content, for example via a PR triggered workflow, can embed escape sequences that are replayed in the user's terminal when they inspect the run.

Depending on the victim's terminal emulator, injected sequences could change the window title, manipulate on screen content, or in some terminal emulators (such as screen) potentially execute arbitrary commands.

In 2.92.0, GitHub CLI sanitizes terminal control sequences in Actions log output before writing to the terminal.

PoC

Create a workflow that emits terminal escape sequences in its log output:

name: Escape Sequence PoC

on:
  workflow_dispatch:

jobs:
  emit-escape-sequences:
    runs-on: ubuntu-latest
    steps:
      - name: Emit terminal escape sequences
        run: |
          # OSC title set
          printf 'ESCAPE_MARKER_START \033]0;HIJACKED_TITLE\007 ESCAPE_MARKER_END\n'
          # CSI color
          printf 'ESCAPE_MARKER_START \033[31mRED_TEXT\033[0m ESCAPE_MARKER_…

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-45803 has been found in github.com/cli/cli/v2.
Attackers can target a specific entry point like screen over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.5/10.
What to do: upgrade github.com/cli/cli/v2 to 2.92.0 or later.
If unsure, ask your IT team or search "github.com/cli/cli/v2 CVE-2026-45803" on the vendor's site.

CVE-2026-45803 (github.com/cli/cli/v2) — CWE-150 / CVSS v3 3.5
Attack vector: remote (network-reachable)
Attack surface: screen
Patched: 2.92.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-150) exists in github.com/cli/cli/v2. Attackers reach the vulnerable code path via screen.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/cli/cli/v2. Attack surface: screen.

🔥 Severity

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

🔧 How to fix

Update to 2.92.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 request patterns matching this CVE's known IOCs. 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
    Apply patch patch 
    Upgrade github.com/cli/cli/v2 to 2.92.0

    ステージング環境で 2.92.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

go github.com/cli/cli/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.92.0"}]}]
go github.com/cli/cli
[{"type":"SEMVER","events":[{"introduced":"1.6.0"},{"last_affected":"1.14.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