CVE-2026-72903
Description
A flaw was found in Tabby, a terminal emulator. A remote attacker, operating a malicious SFTP server, could exploit a path traversal vulnerability. This occurs when the server returns a specially crafted filename containing backslashes, which are then misinterpreted by Tabby's Windows-native path processing. This misinterpretation allows the attacker to create or overwrite files outside the user's selected download or temporary edit directories, leading to arbitrary file write.
Statement
An IMPORTANT severity flaw was found in Tabby (formerly Terminus), a terminal emulator. A remote attacker operating a malicious SFTP server can return filenames containing backslash traversal sequences; Tabby's POSIX-based path processing preserves these backslashes as ordinary filename characters, and when the resulting paths are passed to Windows-native path handling during SFTP folder downloads or remote file editing, Windows interprets them as path separators and parent-directory traversal. This allows attacker-controlled content to be created or overwritten outside the user's selected download directory or temporary edit directory on Windows systems, resulting in an arbitrary file write with high impact to integrity and availability. Exploitation requires user interaction, as the victim must connect to the malicious SFTP server and initiate a download or file-edit operation. Red Hat Product Security rates this flaw IMPORTANT with a CVSS 3.1 score of 8.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H), consistent with the upstream severity assessment. Within the Red Hat portfolio, OpenShift Data Foundation 4.19, 4.20, 4.21, and 4.22 are recorded as affected with a delegated resolution, and a fix is being pursued by the responsible maintaining team.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 8.1 | N/A | 8.1 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | Required | N/A | Required |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
