CVE-2026-44466
Analyzed Analyzed - Analysis Complete
Zed Code Editor Terminal Command Injection via Bash Arithmetic Expansion

Publication date: 2026-05-28

Last updated on: 2026-06-02

Assigner: GitHub, Inc.

Description
Zed is a code editor. Prior to 0.229.0, Zed's terminal tool permission system can be bypassed via bash arithmetic expansion $((...)), allowing execution of arbitrary commands nested inside an allowlisted command like echo. This vulnerability is fixed in 0.229.0.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-28
Last Modified
2026-06-02
Generated
2026-06-18
AI Q&A
2026-05-28
EPSS Evaluated
2026-06-16
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
zed zed to 0.229.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-78 The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Compliance Impact

The vulnerability allows arbitrary command execution on a user's machine by bypassing the terminal tool permission system in Zed. This can lead to significant impacts on confidentiality, integrity, and availability of data.

Such impacts could potentially affect compliance with common standards and regulations like GDPR and HIPAA, which require protection of sensitive data and system integrity. If exploited, this vulnerability might lead to unauthorized data access or modification, violating these regulatory requirements.

However, the provided information does not explicitly mention compliance implications or specific regulatory impacts.

Executive Summary

The vulnerability CVE-2026-44466 affects Zed's terminal tool permission system by allowing an allowlist bypass through Bash arithmetic expansion syntax $((...)).

Zed uses a regex pattern to allow certain commands like 'echo', but this pattern does not account for commands nested inside the $((...)) syntax.

Attackers can embed arbitrary commands inside this syntax, for example: echo $(( $(curl -s https://google.com | wc -l) )), which bypasses the allowlist and executes the nested command.

This means that even if only 'echo' is allowed, an attacker can execute other commands by nesting them inside the arithmetic expansion.

The vulnerability is fixed in Zed version 0.229.0.

Impact Analysis

This vulnerability allows an attacker to execute arbitrary commands on a user's machine if they can influence AI agent tool calls, such as through prompt injection.

The attack requires local access, low complexity, no privileges, and user interaction.

Successful exploitation can lead to significant impacts on confidentiality, integrity, and availability of the affected system.

Detection Guidance

This vulnerability involves bypassing Zed's terminal tool permission system via Bash arithmetic expansion $((...)) inside allowlisted commands like echo.

To detect exploitation attempts on your system, you can monitor command executions that include suspicious use of the $((...)) syntax nested inside allowlisted commands.

  • Use shell history or audit logs to search for commands matching patterns like: echo $(( ... ))
  • Example command to search bash history for suspicious patterns: grep -E 'echo \$\(\(' ~/.bash_history
  • Use system auditing tools (e.g., auditd) to log and review executions of allowlisted commands with nested arithmetic expansions.
Mitigation Strategies

The primary mitigation is to upgrade Zed to version 0.229.0 or later, where this vulnerability has been fixed.

Until the upgrade is applied, avoid relying solely on allowlists for terminal commands in Zed, as they can be bypassed via the described method.

Additionally, restrict local access to trusted users only, since the attack requires local access and user interaction.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-44466. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart