Terminal manipulation via unsanitized workflow log output
Published May 15, 2026 · Updated May 15, 2026
Terminal escape injection in GitHub CLI before 2.92.0 allows remote authenticated users to manipulate terminals through workflow logs. The gh run view --log and --log-failed paths write attacker-influenced Actions log bytes to stdout or a pager without neutralizing control sequences. Exploitation requires a user to inspect the poisoned run; effects range from altered titles and screen content to command execution in Screen terminals.
Summary
What happened
Terminal escape injection in GitHub CLI before 2.92.0 allows remote authenticated users to manipulate terminals through workflow logs. The gh run view --log and --log-failed paths write attacker-influenced Actions log bytes to stdout or a pager without neutralizing control sequences. Exploitation requires a user to inspect the poisoned run; effects range from altered titles and screen content to command execution in Screen terminals.
The record
- CVE
- CVE-2026-45803
- Published
- May 15, 2026
- Updated
- May 15, 2026
- Vendor
- Product
- GitHub CLI
- Classifications
- CWE-150, CAPEC-93, T1204
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 15, 2026CVE publishedPublication date reported by the CVE source.
- May 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.6.0, < 2.92.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub CLI terminal escape sequence proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo