Skip to main content
← Vulnerabilities

dysk before 3.8.2 Terminal Escape Sequence Injection via Mount Metadata

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

1.0LowCNA
Exploited
No known exploitation
Fix
Fixed in 3.8.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.8.2.

1Pcve.now Index 1 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure?/25Exposure: unknown (data gap). No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity1/10CVSS 1.0
  • No patch0/5No signal

What would change the score

  • Would score about 56 if added to CISA KEV
  • Would score about 51 if CISA's SSVC rates exploitation active
  • Would score about 23 if advisories confirm default setups are exposed

CVE-2026-121547 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 1.0 (low) and affects dysk; fixed in 3.8.2.

Published
Last modified
Published
Not listed in CISA KEV
1/100 · provisional
Fix
Fixed in 3.8.2
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

The dysk disk-usage utility, developed by Canop, is affected when it displays mount information in its table and CSV output. A local user can create a mount whose name contains terminal control sequences, which can make dysk's output misleading or hidden and change the terminal window title for another user who runs it.

Read the original 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.

What to do

  • Upgrade to a fixed version: 3.8.2.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • Canop dysk

    fixed in 3.8.2

Evidence 6

  1. Patch
  2. Patch
  3. Report
  4. Repository
  5. Repository
  6. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-121547

Is CVE-2026-121547 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-121547?

dysk: before 3.8.2.Source: cve.now feed data

How do I fix CVE-2026-121547?

Upgrade to a fixed version: 3.8.2.Source: cve.now feed data