Skip to content

Env-var prefixes can lead to denylisted command autoexecution

High
Legoben published GHSA-3839-h8jj-ph82 Jun 9, 2026

Package

Warp

Affected versions

>=v0.2025.10.08.08.12.stable_00,

Patched versions

v0.2026.05.06.15.42.stable_01

Description

Description

Impacted Warp versions contain a command execution permission-check bypass in the default unsandboxed CLI agent profile. The CLI profile is non-interactive and relies on a command denylist as a safety boundary for commands that should require confirmation. Because command strings were checked before canonicalizing leading environment-variable assignments, an attacker who can influence the agent's command output may cause denylisted commands to be treated as non-denylisted.

Impact

Successful exploitation may allow commands that should require confirmation to run under the victim user's local shell authority.

Exploitation requires user interaction: the victim must run the unsandboxed CLI agent on attacker-controlled or prompt-injectable context, or otherwise receive a malicious agent response.

Patch

The patch canonicalizes commands for denylist evaluation by stripping leading environment-variable assignments before applying execution predicates.

Workarounds

Update a patched Warp build. If updating immediately is not possible, avoid running the unsandboxed CLI agent on untrusted or prompt-injectable content.

Credits

Thanks to the following reporter who responsibly disclosed this issue:

References

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

CVE ID

CVE-2026-48721

Weaknesses

Incorrect Behavior Order: Validate Before Canonicalize

The product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step. Learn more on MITRE.

Protection Mechanism Failure

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. Learn more on MITRE.

Credits