# CVE-2026-48721: Warp: Env-var prefixes can lead to denylisted command autoexecution

> Attackers can bypass command denylists in Warp's CLI agent by using environment variable prefixes, leading to unauthorized command execution.

- **Severity:** High 8.6 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-3839-h8jj-ph82

## What is CVE-2026-48721?

CVE-2026-48721 is a high-severity vulnerability in warpdotdev warp, published on 24 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Warp is an agentic development environment. From 0.2025.10.08.08.12.stable_00 until 0.2026.05.06.15.42.stable_01, Warp contains 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. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01.

Weakness: CWE-693 (Protection Mechanism Failure), CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize)

## Which versions are affected by CVE-2026-48721?


## How do I fix CVE-2026-48721?

No fix has been published for CVE-2026-48721 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-48721 being exploited?

There is no known exploitation of CVE-2026-48721 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48721 and fix it if it is affected.

What it is: CVE-2026-48721 is a high-severity vulnerability in warpdotdev warp, published on 24 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-48721 in the wild and no public exploit code.

Affected product: warpdotdev warp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48721/ (Markdown: https://insights.sbomify.com/CVE-2026-48721/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48721
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48721
- OSV: https://osv.dev/vulnerability/CVE-2026-48721

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48721/
Summaries are generated and may contain mistakes; the official description above is the record.