GitHub CLI: GitHub Actions log output in gh run view allows terminal escape sequence injection

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

EPSS

• CVE-2026-45803: 0.21% estimated exploitation activity in the next 30 days; percentile 10.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

19 May 2026, 19:37 UTC

Last modified by the source

19 May 2026, 19:37 UTC

Source last checked

26 Oct 2026, 15:22 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-crc3-h8v6-qh57

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45803

Advisory: GitHub CLI: GitHub Actions log output in `gh run view` allows terminal escape sequence injection
IDs: CVE-2026-45803, GHSA-crc3-h8v6-qh57
Record: https://patchnext.com/advisories/cve-2026-45803 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/cli/cli/v2 2.92.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cli/cli/v2: affected < 2.92.0; fixed in 2.92.0
- Go github.com/cli/cli: affected >= 1.6.0, <= 1.14.0

## Suggested inspection (read-only)
- Go github.com/cli/cli/v2: check the installed version with your package manager.
- Go github.com/cli/cli: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cli/cli/v2, github.com/cli/cli.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-crc3-h8v6-qh57 (GitHub-reviewed advisory GHSA-crc3-h8v6-qh57 lists affected ranges: Go github.com/cli/cli/v2 >=0 =1.6.0 <=1.14.0)

Commands are suggestions: review each one before running it.