CVE-2026-72847

MEDIUMPre-NVD 4.64.6—
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
4.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.6Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.6
EG Score
4.6(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

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 computed
Severity46% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

August 20, 2026

Last Modified

August 21, 2026

Advisory Details (7)

Auto-updated Aug 20, 2026
🔬 Proof of concept available. Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic🟡 PoC Available

broot 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-view
generic

GitHub - Canop/broot: A new way to see and navigate directory trees · GitHub

https://github.com/Canop/broot
generic

broot/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.rs
generic

broot/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.rs
github_commit

commit 0717a94b3c0e (Canop/broot)

Fix landed in Canop/broot commit 0717a94b3c0e — awaiting tagged release

https://github.com/Canop/broot/commit/0717a94b3c0efa19c7bbcfe0fb49a2374752a168
github_commit

commit 4ba40f7d47af (Canop/broot)

Fix landed in Canop/broot commit 4ba40f7d47af — awaiting tagged release

https://github.com/Canop/broot/commit/4ba40f7d47af78457c7656f15eba71d63d97fce5
generic

Tree 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/1188

Vendor 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)
PackageVulnerable rangeFixed inDependents
rust-broot1.46.3-2 ... 1.57.0+ds-3 (27 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rust-broot1.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 20× in last 7d / 85× 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.

  1. 2026-09-19 02:57 UTCEG score recompute
  2. 2026-09-19 02:57 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 05:12 UTCEG score recompute
  5. 2026-09-18 05:12 UTCGHSA enrichment
  6. 2026-09-17 07:27 UTCEG score recompute
  7. 2026-09-17 07:27 UTCGHSA enrichment
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 09:41 UTCEG score recompute
  10. 2026-09-16 09:41 UTCGHSA enrichment
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-15 11:34 UTCEG score recompute
  13. 2026-09-15 11:34 UTCGHSA enrichment
  14. 2026-09-15 03:12 UTCEPSS rescore
  15. 2026-09-14 13:45 UTCEG score recompute
  16. 2026-09-14 13:45 UTCGHSA enrichment
  17. 2026-09-13 15:52 UTCGHSA enrichment
  18. 2026-09-12 18:07 UTCEG score recompute
  19. 2026-09-12 18:07 UTCGHSA enrichment
  20. 2026-09-12 15:02 UTCEPSS rescore
  21. 2026-09-11 20:20 UTCEG score recompute
  22. 2026-09-11 20:20 UTCGHSA enrichment
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-10 22:35 UTCEG score recompute
  25. 2026-09-10 22:35 UTCGHSA enrichment
Show 60 more
  1. 2026-09-10 09:35 UTCEPSS rescore
  2. 2026-09-10 00:49 UTCGHSA enrichment
  3. 2026-09-09 01:57 UTCEG score recompute
  4. 2026-09-09 01:57 UTCGHSA enrichment
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-08 02:18 UTCEG score recompute
  7. 2026-09-08 02:18 UTCGHSA enrichment
  8. 2026-09-07 04:32 UTCEG score recompute
  9. 2026-09-07 04:32 UTCGHSA enrichment
  10. 2026-09-06 13:48 UTCEPSS rescore
  11. 2026-09-06 06:34 UTCEG score recompute
  12. 2026-09-06 06:34 UTCGHSA enrichment
  13. 2026-09-05 08:50 UTCEG score recompute
  14. 2026-09-05 08:50 UTCGHSA enrichment
  15. 2026-09-04 11:04 UTCEG score recompute
  16. 2026-09-04 11:04 UTCGHSA enrichment
  17. 2026-09-04 05:07 UTCEPSS rescore
  18. 2026-09-03 13:06 UTCGHSA enrichment
  19. 2026-09-02 15:12 UTCEG score recompute
  20. 2026-09-02 15:12 UTCGHSA enrichment
  21. 2026-09-02 14:12 UTCEPSS rescore
  22. 2026-09-01 17:14 UTCEG score recompute
  23. 2026-09-01 17:14 UTCGHSA enrichment
  24. 2026-09-01 13:54 UTCEPSS rescore
  25. 2026-09-01 04:40 UTCEPSS rescore
  26. 2026-09-01 04:40 UTCEPSS rescore
  27. 2026-08-31 19:04 UTCGHSA enrichment
  28. 2026-08-30 21:00 UTCEG score recompute
  29. 2026-08-30 21:00 UTCGHSA enrichment
  30. 2026-08-30 19:18 UTCEPSS rescore
  31. 2026-08-30 19:17 UTCEPSS rescore
  32. 2026-08-30 01:22 UTCEPSS rescore
  33. 2026-08-29 23:15 UTCGHSA enrichment
  34. 2026-08-29 01:28 UTCEG score recompute
  35. 2026-08-29 01:28 UTCGHSA enrichment
  36. 2026-08-28 21:42 UTCEPSS rescore
  37. 2026-08-28 01:40 UTCEG score recompute
  38. 2026-08-28 01:40 UTCGHSA enrichment
  39. 2026-08-27 14:25 UTCEPSS rescore
  40. 2026-08-27 03:55 UTCEG score recompute
  41. 2026-08-27 03:55 UTCGHSA enrichment
  42. 2026-08-26 14:47 UTCEPSS rescore
  43. 2026-08-26 06:10 UTCGHSA enrichment
  44. 2026-08-25 08:24 UTCEG score recompute
  45. 2026-08-25 08:24 UTCGHSA enrichment
  46. 2026-08-24 10:35 UTCEG score recompute
  47. 2026-08-24 10:35 UTCGHSA enrichment
  48. 2026-08-23 12:50 UTCGHSA enrichment
  49. 2026-08-22 15:06 UTCEG score recompute
  50. 2026-08-22 15:06 UTCGHSA enrichment
  51. 2026-08-21 23:49 UTCEPSS rescore
  52. 2026-08-21 17:21 UTCEG score recompute
  53. 2026-08-21 17:21 UTCGHSA enrichment
  54. 2026-08-21 16:29 UTCEG score recompute
  55. 2026-08-21 16:29 UTCGHSA enrichment
  56. 2026-08-21 16:02 UTCEG score recompute
  57. 2026-08-21 16:02 UTCGHSA enrichment
  58. 2026-08-20 18:17 UTCEG score recompute
  59. 2026-08-20 17:32 UTCEG score recompute
  60. 2026-08-20 17:31 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72847?
CVE-2026-72847 is a medium vulnerability published on August 20, 2026. broot renders each file and directory name in its interactive tree view exactly as read from the filesystem. Names are converted with a plain tostringlossy() call in src/treebuild/builder.rs and in TreeLine::unprune in src/tree/treeline.rs, and no control-character filtering exists anywhere in the…
When was CVE-2026-72847 disclosed?
CVE-2026-72847 was first published in the National Vulnerability Database on August 20, 2026, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72847 actively exploited?
CVE-2026-72847 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.9% of all scored CVEs.
What is the CVSS score of CVE-2026-72847?
CVE-2026-72847 has a CVSS v3 base score of 4.6 (NVD).
How do I remediate CVE-2026-72847?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72847, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-72847

Explore →

Is Your Infrastructure Affected by CVE-2026-72847?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs