CVE-2026-72847

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account, but needs a user to act. Limited direct impact.

Exploit odds

0.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-08-20 18:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-18 20:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.1% in the next 30 days (EPSS).
• Severity: 2.4 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-08-20 18:16 UTC

Last modified

2026-10-18 20:10 UTC

Exploit probability

0.1% · EPSS, next 30 days

Weakness

CWE-150

Record status

Deferred

Attack profile CVSS 4.0 · 2.4

Attack vector

Local

Complexity

Low

Attack requirements

None

Privileges needed

Low

User interaction

Passive

Confidentiality

Low

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-72847.md and follow it. Check whether this project is affected by CVE-2026-72847. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge