CVE-2026-72847: Canop broot · Improper Neutralization of Escape, Meta, or Control Sequences
Affects Canop brootSource CVE Database V5
Not known to be exploited · CVSS 2.4 Low.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Canopbroot | Affected
| Fixed in– |
GitHubbrootpkg:github/brootOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, users should be cautious when browsing directories containing files created by untrusted local users.
Description
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.
References
- github.com/Canop/broot/issues/1188 (opens in a new tab)
- github.com/Canop/broot/commit/4ba40f7d47af78457c7656f15eba71d63d97fce5 (opens in a new tab)
- github.com/Canop/broot/commit/0717a94b3c0efa19c7bbcfe0fb49a2374752a168 (opens in a new tab)
- github.com/Canop/broot/blob/v1.58.0/src/tree/tree_line.rs (opens in a new tab)
- github.com/Canop/broot/blob/v1.58.0/src/tree_build/builder.rs (opens in a new tab)
- github.com/Canop/broot (opens in a new tab)
- vulncheck.com/advisories/broot-terminal-escape-sequence-injection-via-unsanitized-file-and-directory-names-in-the-tree-view (opens in a new tab)