# CVE-2026-48725: Warp may allow terminal output to access the local clipboard through OSC 52

> Attackers can read or write the local clipboard via malicious terminal output in Warp, bypassing user confirmation prompts.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **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-wgqj-4c26-7c4g

## What is CVE-2026-48725?

CVE-2026-48725 is a high-severity vulnerability in warpdotdev warp, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Warp is an agentic development environment. From 0.2021.04.25.23.05.stable_00 until 0.2026.05.06.15.42.stable_01, Warp allows terminal output to request access to the local system clipboard. A malicious remote host, remote program, or other attacker-controlled terminal output source can trigger clipboard reads or writes without a separate confirmation step. This crosses the trust boundary between untrusted terminal output and the user's local desktop clipboard. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01.

Weakness: CWE-276 (Incorrect Default Permissions)

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


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

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

## Is CVE-2026-48725 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48725 is a high-severity vulnerability in warpdotdev warp, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-48725 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-48725/ (Markdown: https://insights.sbomify.com/CVE-2026-48725/index.md)
```

## Sources

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

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