Improper Neutralization Affecting rust-broot package, versions *


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.1% (2nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-RUSTBROOT-19166205
  • published22 Aug 2026
  • disclosed20 Aug 2026

Introduced: 20 Aug 2026

NewCVE-2026-72847  (opens in a new tab)
CWE-150  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest rust-broot.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-broot package and not the rust-broot package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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 Base Scores

version 3.1