Quick answers
- Is CVE-2026-45036 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45036 being exploited in the wild.
- How severe is CVE-2026-45036?
- High severity, with a CVSS score of 7, published 15 May 2026.
- Which products and versions are affected?
- Eugeny Tabby < 1.0.233.
- Is there a fix for CVE-2026-45036?
- 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-45036 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-45036?
- 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
The vulnerability exists in the ZModemMiddleware component of tabby-terminal, which monitors session output for ZMODEM ZRQINIT headers. When a header is detected, the middleware unconditionally calls detection.confirm() and writes a fixed ZRINIT response back into the active pseudo-terminal (PTY) as input without user interaction. If a user 'cats' a malicious file, these injected bytes are buffered and then executed by the shell (fish, bash, or zsh) once the initial process exits. Attackers can use glob expansion (e.g., '**') or terminal color-query feedback (OSC 10) to construct a command path that executes a local malicious binary, bypassing PATH restrictions. The issue is fixed in version 1.0.233.
Affected products
- Eugeny Tabby < 1.0.233
Timeline
- 2026-05-07: advisory: GitHub advisory published by maintainer
- 2026-05-15: disclosed: CVE published to NVD