dbcve.org
TabbyApplication

CVE-2026-45036

HIGH · 7.0 CVSS v3.1 Published 2026-05-15
Fix available
A fix is available. Upgrade to 1.0.233 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Tabby (formerly Terminus) is a highly configurable terminal emulator. Prior to 1.0.233, Tabby before 1.0.233 automatically confirms ZMODEM protocol detection on all terminal session output without user interaction, enabling shell command execution when a user displays attacker-controlled content. The ZModemMiddleware in tabby-terminal consumes all session output through a Zmodem.Sentry, and when a ZMODEM ZRQINIT header is detected, unconditionally calls detection.confirm() and writes a fixed ZRINIT response ( **\x18B0100000023be50\r\n\x11) back into the active PTY as input. When the process that triggered the detection (e.g., cat) exits, the injected bytes are consumed by the user's shell as a command line. Under fish (default configuration), the ** prefix triggers recursive glob expansion against the current directory, allowing an attacker-placed executable at a matching nested path (e.g., d/xB0100000023be50) to be executed by relative pathname without relying on PATH. Under bash and zsh, a secondary xterm.js terminal color-query feedback (OSC 10) can be combined in the same file to inject a slash-containing command word that similarly bypasses PATH resolution. An attacker can exploit this by providing a crafted file (e.g., in a cloned Git repository) that a user displays with cat, achieving code execution with no interaction beyond viewing the file. This vulnerability is fixed in 1.0.233.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Tabby terminal emulator prior to 1.0.233 automatically confirms ZMODEM protocol detection by writing a fixed ZRINIT response into the PTY when ZRQINIT header is detected in session output, without user interaction. These injected bytes are interpreted as shell input, allowing command execution when users view attacker-crafted files using cat.

MitigationUpgrade Tabby to version 1.0.233 or later to address the automatic ZMODEM confirmation vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TabbyApplication
Affected:< 1.0.233

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Tabby is installed
    Look for Tabby terminal emulator in your installed applications. On Linux check /opt/tabby or your package manager. On Windows check Program Files. On macOS check Applications folder.
    Affected if Tabby terminal emulator is not found on the system, so this CVE does not apply.
  2. Determine installed Tabby version
    Run 'tabby --version' from command line, or right-click the Tabby application and select About/Properties to view the version number.
    Affected if Unable to determine the installed version.
  3. Compare version against affected range
    Compare the installed version number to 1.0.233. Any version prior to 1.0.233 (such as 1.0.232, 1.0.230, etc.) is within the affected range.
    Affected if Installed version is 1.0.232 or lower.
  4. Verify ZMODEM trigger condition
    This vulnerability triggers when viewing attacker-crafted files using 'cat' in a Tabby terminal session. The flaw is in how Tabby automatically responds to ZRQINIT headers from ZMODEM file transfer protocol.
    Affected if You use Tabby to view files from untrusted sources via cat command, and your version is below 1.0.233.

You are affected if Tabby terminal emulator is installed and the version is below 1.0.233.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.233 or later
Fixed in 1.0.233
Interim mitigation

Upgrade Tabby to version 1.0.233 or later to address the automatic ZMODEM confirmation vulnerability.

Recommended fix High confidence

1.0.233

  1. 1. Check current Tabby version by navigating to Help > About in the application menu
  2. 2. Download Tabby version 1.0.233 or later from the official GitHub releases page (github.com/Eugeny/tabby/releases)
  3. 3. Close any running Tabby instances
  4. 4. Install the updated version (either via installer or by replacing the application files)
  5. 5. Restart Tabby and verify the version in Help > About shows 1.0.233 or higher
  6. 6. As a precaution, avoid using 'cat' or similar commands to view files from untrusted sources (especially in cloned Git repositories) until the upgrade is complete

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tabby Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45036 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45036 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data