Quick answers
- Is CVE-2026-45038 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45038 being exploited in the wild.
- How severe is CVE-2026-45038?
- Informational severity, with a CVSS score of 8.4, published 15 May 2026.
- Which products and versions are affected?
- Eugeny Tabby < 1.0.233.
- Is there a fix for CVE-2026-45038?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-45038 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-45038?
- Check whether you run Eugeny Tabby at an affected version. 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
A vulnerability in Tabby terminal emulator versions prior to 1.0.233 stems from improper neutralization of escape, meta, or control sequences (CWE-150) during drag-and-drop operations. When a file is dropped into the terminal, Tabby fails to escape control characters within the file path. An attacker can craft a filename containing control sequences such as 'End of Text' (\x03) to terminate a running process and 'Carriage Return' (\x0d) to execute a new command. While the attack requires local user interaction, malicious filenames can be padded with junk text to hide the payload from the user's file manager view. The issue is resolved in version 1.0.233 by properly escaping control characters in file paths.
Affected products
- Eugeny Tabby < 1.0.233
Timeline
- 2026-05-07: advisory: Vendor advisory published on GitHub
- 2026-05-15: disclosed: CVE published to NVD