# CVE-2026-72847: broot Terminal Escape Sequence Injection via Unsanitized File and Directory Names in the Tree View

> Attackers can inject terminal escape sequences via malicious filenames, potentially executing code or stealing data when victims browse directories.

- **Severity:** Low 2.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-72847, GHSA-8v8c-hvqj-mqw8, UBUNTU-CVE-2026-72847, openSUSE-SU-2026:21675-1

## What is CVE-2026-72847?

CVE-2026-72847 is a low-severity vulnerability in Canop broot, published on 20 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-150 (Improper Neutralization of Escape, Meta, or Control Sequences)

## Which versions are affected by CVE-2026-72847?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `broot` | openSUSE:Leap 16.0 | All versions | 1.59.0-bp160.1.1 |

## How do I fix CVE-2026-72847?

Apply the vendor's patch.

## Is CVE-2026-72847 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72847 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72847 and fix it if it is affected.

What it is: CVE-2026-72847 is a low-severity vulnerability in Canop broot, published on 20 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72847 exists.

Affected product: Canop broot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72847/ (Markdown: https://insights.sbomify.com/CVE-2026-72847/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72847
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72847
- OSV: https://osv.dev/vulnerability/CVE-2026-72847

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72847/
Summaries are generated and may contain mistakes; the official description above is the record.