CVE-2022-41138: Zutty · Code Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 0.13 as a priority.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 2.2% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.13
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade tomszilagyi/zutty to 0.13.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubtomszilagyi/zuttypkg:github/tomszilagyi/zuttyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Given the critical nature of CVE-2022-41138, European organizations should take immediate and specific mitigation steps beyond generic advice: 1) Identify and inventory all systems using Zutty terminal emulator versions prior to 0.13. 2) Upgrade Zutty to version 0.13 or later as soon as an official patch or update is available. 3) Implement strict input validation and filtering on any interfaces that accept terminal input sequences, especially those exposed to untrusted networks or users. 4) Employ network segmentation and firewall rules to limit access to systems running Zutty terminals, reducing exposure to potential attackers. 5) Monitor logs and terminal activity for unusual or suspicious DECRQSS control sequences or other anomalous terminal behavior. 6) Educate system administrators and developers about the risks of terminal escape sequences and encourage the use of safer terminal emulators or configurations that disable risky control sequences. 7) Establish incident response plans specifically addressing terminal-based code execution threats to enable rapid containment and remediation if exploitation is detected.
Description
In Zutty before 0.13, DECRQSS in text written to the terminal can achieve arbitrary code execution.