CVE-2026-72847

MEDIUMPre-NVD 4.64.6
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.6 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:vulncheck
4.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 4.6Exploit: None knownExposed: 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(low)
EG Risk
25(Track)
EG Risk 25/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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

August 20, 2026

Last Modified

August 20, 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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 2× 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-08-20 17:32 UTCEG score recompute
  2. 2026-08-20 17:31 UTCMITRE cvelistV5first tracked

Frequently asked(4)

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. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-72847?
CVE-2026-72847 has a CVSS v4.0 base score of 4.6 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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

Explore the affected products and dependency analysis for 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