Terminal state manipulation via unsanitized quit output
Published Aug 13, 2026 · Updated Aug 13, 2026
Terminal injection in gdu allows local users to alter terminal state through crafted file or directory names printed after TUI exit. The doQuit and printMarkedPaths paths write currentDirPath and markedPaths directly to os.Stdout after tview protection ends, without stripping control characters. Exploitation requires a local user to run the TUI, enter or mark an attacker-named filesystem entry, and quit; effects depend on the terminal emulator and include title or clipboard manipulation.
Summary
What happened
Terminal injection in gdu allows local users to alter terminal state through crafted file or directory names printed after TUI exit. The doQuit and printMarkedPaths paths write currentDirPath and markedPaths directly to os.Stdout after tview protection ends, without stripping control characters. Exploitation requires a local user to run the TUI, enter or mark an attacker-named filesystem entry, and quit; effects depend on the terminal emulator and include title or clipboard manipulation.
The record
- CVE
- CVE-2026-73480
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Daniel Milde
- Product
- gdu
- Classifications
- CWE-116, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 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=0 <fe605ec
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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