# CVE-2026-121547: dysk before 3.8.2 Terminal Escape Sequence Injection via Mount Metadata


- **Severity:** Low 1.0 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** GHSA-69c2-wcm2-5698

## What is CVE-2026-121547?

CVE-2026-121547 is a low-severity vulnerability in Canop dysk, published on 3 Nov 2026. 

### Official description

Canop dysk before 3.8.2 contains a terminal escape sequence injection vulnerability that allows local users to inject control sequences by crafting mount metadata rendered unsanitized in table and CSV output. Attackers can create FUSE mounts with ESC/OSC sequences in mount-point names or fsname, causing spoofed or hidden output and window-title changes when another user runs dysk.

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

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


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

No fix has been published for CVE-2026-121547 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121547 being exploited?

There is no known exploitation of CVE-2026-121547 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121547 is a low-severity vulnerability in Canop dysk, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121547 in the wild and no public exploit code.

Affected product: Canop dysk. 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-121547/ (Markdown: https://insights.sbomify.com/CVE-2026-121547/index.md)
```

## Sources

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

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