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.
CVE-2026-72847
Score 4.6 from GitHub Security Advisory (severity: LOW) published 2026-08-20. A secondary CVSS source baseline 4.6; sources differ by 0.0.
- Lower severity and no public exploit yet
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 4.6
- EG Score
- 4.6MEDIUMmedium confidence
- EG Risk
- 37EG Risk 37/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity46% × 45%Exploitation40% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release. - EPSS PROB
- 0.1%
- EPSS %ILE
- 3rd
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
August 20, 2026
Last Modified
September 24, 2026
Advisory Details (7)
Auto-updated Aug 20, 2026broot Terminal Escape Sequence Injection via Unsanitized File and Directory Names in the Tree View | Advisories | VulnCheck
https://www.vulncheck.com/advisories/broot-terminal-escape-sequence-injection-via-unsanitized-file-and-directory-names-in-the-tree-viewGitHub - Canop/broot: A new way to see and navigate directory trees · GitHub
https://github.com/Canop/brootbroot/src/tree_build/builder.rs at v1.58.0 · Canop/broot · GitHub
https://github.com/Canop/broot/blob/v1.58.0/src/tree_build/builder.rsbroot/src/tree/tree_line.rs at v1.58.0 · Canop/broot · GitHub
https://github.com/Canop/broot/blob/v1.58.0/src/tree/tree_line.rscommit 0717a94b3c0e (Canop/broot)
Fix landed in Canop/broot commit 0717a94b3c0e — awaiting tagged release
https://github.com/Canop/broot/commit/0717a94b3c0efa19c7bbcfe0fb49a2374752a168commit 4ba40f7d47af (Canop/broot)
Fix landed in Canop/broot commit 4ba40f7d47af — awaiting tagged release
https://github.com/Canop/broot/commit/4ba40f7d47af78457c7656f15eba71d63d97fce5Tree view does not strip terminal escape sequences from file/directory names, allowing injection via a crafted filename · Issue #1188 · Canop/broot · GitHub
https://github.com/Canop/broot/issues/1188Vendor Advisories for CVE-2026-72847(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 2 ecosystems)
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rust-broot | 1.46.3-2 ... 1.57.0+ds-3 (27 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rust-broot | 1.46.3-2 ... 1.57.0+ds-3 (27 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 75× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 123 total refreshes for this CVE.
- 2026-10-05 01:35 UTCEG score recompute
- 2026-10-05 01:35 UTCGHSA enrichment
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-04 02:39 UTCEG score recompute
- 2026-10-04 02:39 UTCGHSA enrichment
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-03 01:36 UTCEG score recompute
- 2026-10-03 01:36 UTCGHSA enrichment
- 2026-10-02 03:44 UTCEG score recompute
- 2026-10-02 03:44 UTCGHSA enrichment
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-10-01 05:59 UTCEG score recompute
- 2026-10-01 05:59 UTCGHSA enrichment
- 2026-09-30 08:14 UTCEG score recompute
- 2026-09-30 08:14 UTCGHSA enrichment
- 2026-09-28 22:33 UTCEG score recompute
- 2026-09-28 22:33 UTCGHSA enrichment
- 2026-09-28 13:52 UTCEPSS rescore
- 2026-09-28 00:47 UTCEG score recompute
- 2026-09-28 00:47 UTCGHSA enrichment
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-27 03:02 UTCEG score recompute
- 2026-09-27 03:02 UTCGHSA enrichment
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-24 20:15 UTCEG score recompute
Show 75 moreShow fewer
- 2026-09-24 20:15 UTCGHSA enrichment
- 2026-09-24 14:58 UTCEG score recompute
- 2026-09-24 14:58 UTCGHSA enrichment
- 2026-09-23 20:05 UTCEG score recompute
- 2026-09-23 20:05 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 19:45 UTCEG score recompute
- 2026-09-22 19:45 UTCGHSA enrichment
- 2026-09-21 21:09 UTCEPSS rescore
- 2026-09-21 20:12 UTCGHSA enrichment
- 2026-09-20 22:27 UTCGHSA enrichment
- 2026-09-20 00:42 UTCEG score recompute
- 2026-09-20 00:42 UTCGHSA enrichment
- 2026-09-19 02:57 UTCEG score recompute
- 2026-09-19 02:57 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 05:12 UTCEG score recompute
- 2026-09-18 05:12 UTCGHSA enrichment
- 2026-09-17 07:27 UTCEG score recompute
- 2026-09-17 07:27 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 09:41 UTCEG score recompute
- 2026-09-16 09:41 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 11:34 UTCEG score recompute
- 2026-09-15 11:34 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 13:45 UTCEG score recompute
- 2026-09-14 13:45 UTCGHSA enrichment
- 2026-09-13 15:52 UTCGHSA enrichment
- 2026-09-12 18:07 UTCEG score recompute
- 2026-09-12 18:07 UTCGHSA enrichment
- 2026-09-12 15:02 UTCEPSS rescore
- 2026-09-11 20:20 UTCEG score recompute
- 2026-09-11 20:20 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 22:35 UTCEG score recompute
- 2026-09-10 22:35 UTCGHSA enrichment
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-10 00:49 UTCGHSA enrichment
- 2026-09-09 01:57 UTCEG score recompute
- 2026-09-09 01:57 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 02:18 UTCEG score recompute
- 2026-09-08 02:18 UTCGHSA enrichment
- 2026-09-07 04:32 UTCEG score recompute
- 2026-09-07 04:32 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 06:34 UTCEG score recompute
- 2026-09-06 06:34 UTCGHSA enrichment
- 2026-09-05 08:50 UTCEG score recompute
- 2026-09-05 08:50 UTCGHSA enrichment
- 2026-09-04 11:04 UTCEG score recompute
- 2026-09-04 11:04 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 13:06 UTCGHSA enrichment
- 2026-09-02 15:12 UTCEG score recompute
- 2026-09-02 15:12 UTCGHSA enrichment
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 17:14 UTCEG score recompute
- 2026-09-01 17:14 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 19:04 UTCGHSA enrichment
- 2026-08-30 21:00 UTCEG score recompute
- 2026-08-30 21:00 UTCGHSA enrichment
- 2026-08-30 19:18 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 23:15 UTCGHSA enrichment
- 2026-08-29 01:28 UTCEG score recompute
- 2026-08-29 01:28 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 01:40 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-72847?
When was CVE-2026-72847 disclosed?
Is CVE-2026-72847 actively exploited?
What is the CVSS score of CVE-2026-72847?
How do I remediate CVE-2026-72847?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-72847
Is Your Infrastructure Affected by CVE-2026-72847?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.