broot Terminal Escape Sequence Injection via Unsanitized File and Directory Names in the Tree View
Published Aug 20, 2026 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
broot Terminal Escape Sequence Injection via Unsanitized File and Directory Names in the Tree View
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
broot renders each file and directory name in its interactive tree view exactly as read from the filesystem. Names are converted with a plain to_string_lossy() call in src/tree_build/builder.rs and in TreeLine::unprune in src/tree/tree_line.rs, and no control-character filtering exists anywhere in the code, even though the doc comment on the TreeLine name field states that some characters may have been stripped. Any local user who can create a file can therefore place an escape sequence in its name and have it written unmodified to the terminal of anyone who browses that directory, between broot's own styling codes. A reported proof of concept used an OSC 52 clipboard-write sequence and captured the raw bytes broot wrote to its pty, confirming the sequence reaches the terminal unstripped. What an injected OSC or CSI sequence can then do depends on the terminal emulator in use. Browsing a directory is broot's primary function and carries no expectation that the content is trusted.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- GitHub advisory ↗
- Patch commit ↗
- Patch commit ↗
- Source repository ↗
- Source repository ↗
- Source repository ↗
- VulnCheck Advisory: broot Terminal Escape Sequence Injection via Unsanitized File and Directory Names in the Tree View ↗
Record history
Published Aug 20, 2026 · Last refreshed Nov 3, 2026