Quick answers
- Is CVE-2026-54057 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54057 being exploited in the wild.
- How severe is CVE-2026-54057?
- Informational severity, with a CVSS score of 7.3, published 12 June 2026.
- Which products and versions are affected?
- kovidgoyal kitty < 0.47.3.
- Is there a fix for CVE-2026-54057?
- A patch was published on 2026-06-12: Fixed in version 0.47.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54057 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-54057?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Kitty terminal versions prior to 0.47.3 are vulnerable to a command injection flaw similar to historic xterm vulnerabilities. The root cause is located in the OSC 21 (color-control) handler, where the terminal reflects unknown query keys back into the reply without proper sanitization. Because the terminal's VT parser does not treat newlines as terminators for these sequences, an attacker can embed newline characters within a query. When the terminal sends the reply back to the child process (the shell), these newlines cause the shell to interpret the subsequent attacker-controlled bytes as new, independent commands. Exploitation occurs when a user displays malicious escape sequences, such as by 'cat-ing' a crafted text file. This has been patched in version 0.47.3.
Affected products
- kovidgoyal kitty < 0.47.3
Timeline
- 2026-06-12: disclosed
- 2026-06-12: advisory
- 2026-06-12: patched: Fixed in version 0.47.3