Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain push access to shared/forked repo
-
DeliveryPublish branch with shell-metacharacter name
-
ExploitVictim opens repo in Warp
-
ExecutionVictim clicks malicious branch chip
-
PersistBranch name concatenated into shell command
-
ImpactArbitrary command executes as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires (1) the attacker to be able to publish a branch to a Git repository the victim opens in Warp - i.e. write/push access to a shared or forked remote; (2) the victim running an affected Warp version (0.2025.08.06.08.12.stable_00 through pre-0.2026.05.06.15.42.stable_01); and (3) the victim actively selecting the malicious branch from the prompt branch-selector chip in the UI (UI:R) - the payload does not fire automatically on clone/pull. Limiting factors: the mandatory victim click, the need for the victim to have the repo opened in Warp, and the attacker first obtaining branch-publishing access to a repo the victim trusts enough to open. |
| Impact | The supplied CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, base 8.0) reflects high confidentiality, integrity, and availability impact since injected commands run with the victim user's privileges. The two genuine brakes on real-world risk are UI:R (the victim must actively select the malicious branch from the chip UI) and the prerequisite that the attacker can publish a branch to a repo the victim opens - meaningful but not exotic in shared/forked repository workflows. No EPSS score was provided, the CVE is not in CISA KEV, and no public PoC was supplied, so there is no signal of active exploitation; this reads as a real but not emergency priority - a credible social-engineering/supply-chain vector rather than mass-exploited. One nuance to verify: CVSS marks AV:N, but the actual execution trigger is local user interaction inside the desktop app after pulling attacker content, so the 'network' rating reflects how the malicious branch is delivered, not remote unauthenticated execution. |
| Exploit ScenarioDerived | An attacker with push access to a shared or forked Git repository creates a branch whose name embeds shell metacharacters (e.g. a command substitution payload). When a victim opens that repository in an affected Warp version and clicks the branch in the prompt's branch-selector chip, Warp formats the branch name into a checkout command and the shell executes the attacker's embedded command with the victim's privileges. No public PoC was provided, but the low attack complexity (AC:L) makes the payload straightforward once the victim is induced to select the branch. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 24, 2026
Command injection in Warp's prompt branch-selector chip lets a crafted Git branch name execute in the victim's shell when they click that branch in the UI. It affects Warp builds from 0.2025.08.06.08.12.stable_00 up to the fix in 0.2026.05.06.15.42.stable_01, and is exploitable by anyone able to publish a branch to a repository the victim opens in Warp. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
RemediationAI
Vendor-released patch: upgrade Warp to 0.2026.05.06.15.42.stable_01 or later, which replaces raw string command formatting with a typed PromptChipShellCommand enum (GitCheckout, GitCreateAndCheckoutBranch, ChangeDirectory, NvmUse, etc.) so user-controlled values can no longer be concatenated into shell command lines; see the advisory at https://github.com/warpdotdev/warp/security/advisories/GHSA-hgvx-4xvm-39pw and commit 4295ec08d01912fe355351547e541277f29288cd. Until you can update, the practical compensating control is behavioral: do not click the branch-selector chip in the prompt for repositories that accept branches from untrusted contributors (forks, shared remotes), and instead check out branches by typing the git command manually after inspecting the branch name - the trade-off is loss of the one-click chip convenience. Reviewing/renaming suspicious branch names before interacting with them in Warp further reduces exposure.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Warp is an agentic terminal/development environment written in Rust. The affected feature renders interactive 'context chips' in the prompt - including a branch selector that, when clicked, runs a Git command such as a checkout for the selected branch. Per the commit diff (4295ec08), the vulnerable code built these commands by string formatting (format_git_branch_command, format_create_git_branch_command, format_change_directory_command) and passing a raw String to TryExecuteCommand/TryExecuteChipCommand. Because a Git branch name is attacker-controllable text that was concatenated directly into a shell command line, this is a classic CWE-78 OS Command Injection: shell metacharacters embedded in the branch name are interpreted by the shell. CPE cpe:2.3:a:warpdotdev:warp:*:*:*:*:*:*:*:* identifies the affected product as Warp (vendor warpdotdev).
Know when Warp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Malicious branch is delivered via a remote repo (AV:N) but needs branch-publish access (PR:L) and a victim click on the chip (UI:R); injected shell command runs with full C/I/A impact at user privilege.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
Warp is an agentic development environment. From 0.2025.08.06.08.12.stable_00 until 0.2026.05.06.15.42.stable_01, Warp contains a command injection in the prompt branch selector. A user who can publish a branch to a Git repository opened in Warp can cause a crafted branch name to be interpreted by the victim's shell if the victim selects that branch from the UI. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01.
Executive ViewAI
Warp terminal users running versions prior to 0.2026.05.06.15.42.stable_01 are vulnerable to arbitrary command execution through maliciously crafted Git branch names, enabling attackers with repository access to execute shell commands directly on developers' machines. Though no public exploit has been identified, the vulnerability poses an immediate risk to development environment integrity and access to sensitive credentials. Expedited patching is critical to prevent unauthorized access across the engineering organization.
Apply vendor patch: upgrade to Warp 0.2026.05.06.15.42.stable_01 or later.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
It was possible to bypass policies configured for Zero Trust Secure Web Gateway by using warp-cli 'set-custom-endpoint'
Command injection in Warp's legacy SSH background command path lets an attacker-controlled remote host inject shell synt
Arbitrary code execution in the Warp agentic development environment (builds 0.2023.10.24.08.03.stable_00 through 0.2026
Arbitrary local file write in Warp terminal (0.2025.03.05.08.02.stable_00 through builds before 0.2026.05.06.15.42.stabl
Using warp-cli command "add-trusted-ssid", a user was able to disconnect WARP client and bypass the "Lock WARP switch" f
Command-execution permission bypass in Warp's default unsandboxed CLI agent profile (versions 0.2025.10.08.08.12.stable_
Clipboard hijacking in the Warp agentic terminal (versions 0.2021.04.25.23.05.stable_00 through 0.2026.05.06.15.42.stabl
Command injection in the Warp agentic development environment (Linux builds 0.2024.02.20.08.01.stable_01 through pre-0.2
OS command injection in Warp's AI Agent code-search tooling allows attacker-controlled inputs to escape read-only search
Due to a hardlink created in the ProgramData folder during the repair process of the software, the installer (MSI) of WA
An unprivileged (non-admin) user can exploit an Improper Access Control vulnerability in the Cloudflare WARP Client for
By using warp-cli subcommands (disable-ethernet, disable-wifi), it was possible for a user without admin privileges to b
EUVD-2026-39001
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB