CVE-2026-48720: Warp Terminal Arbitrary File Write via OSC 1337 Escape Sequence

Technical summary

CVE-2026-48720 exploits Warp's handling of ANSI/xterm OSC 1337 File escape sequences. The OSC 1337 protocol is a legitimate mechanism for terminal applications to transfer files, but Warp's implementation fails to validate the source or intent of these payloads. An attacker who can control terminal output seen by a Warp user—whether through a compromised remote server, a malicious GitHub repository with crafted CI/CD output, or similar vectors—can inject non-inline OSC 1337;File sequences that Warp will automatically decode and materialize as files in the user's filesystem. The vulnerability stems from insufficient input validation (CWE-20) and improper file upload handling (CWE-73). The absence of a confirmation dialog or user notification means users remain unaware that files have been written.

Business impact

For development teams using Warp, this vulnerability presents a supply-chain risk. Developers who clone repositories with malicious CI/CD workflows, pull from compromised package registries, or SSH into untrusted systems could unknowingly have arbitrary code or configuration files written to their local machines. This could lead to credential harvesting, injection of backdoors into source code, replacement of legitimate binaries, or lateral movement to other systems on the developer's network. Organizations heavily invested in Warp as their standard development shell face elevated risk until patches are deployed.

Affected systems

Warp versions 0.2025.03.05.08.02.stable_00 through 0.2026.05.06.15.42.stable_00 are vulnerable. The patch is available in version 0.2026.05.06.15.42.stable_01 and later. This affects any user running Warp on macOS, Linux, or other supported platforms during the vulnerable window.

Exploitability

Exploitability is high. The attack requires only that a user interact with untrusted terminal output while Warp is running—a routine occurrence in development workflows. No special privileges, authentication, or complex interaction is needed beyond the user's normal terminal activity. The CVSS 3.1 score of 8.8 (HIGH) reflects network-reachable attack surface, low complexity, and the ability to achieve confidentiality, integrity, and availability impact. The vulnerability is not currently listed in CISA's Known Exploited Vulnerabilities catalog, but the simplicity of the attack vector makes exploitation likely once the vulnerability gains wider awareness.

Remediation

Users must update Warp to version 0.2026.05.06.15.42.stable_01 or later. The update mechanism varies by platform; most users can trigger an update check within Warp's settings or allow automatic updates if enabled. Administrators should prioritize this update across development teams, as the vulnerability is trivial to exploit and affects routine developer workflows.

Patch guidance

Upgrade Warp to 0.2026.05.06.15.42.stable_01 or any subsequent release. Verify the version in Warp's about dialog (typically found in the application menu). For organizations using managed software distribution, push the update to all endpoints running Warp. If Warp is installed via package managers (Homebrew, apt, etc.), standard update procedures should retrieve the patched version. No configuration changes or workarounds are available for unpatched versions.

Detection guidance

Monitor for unexpected file creation in user home directories and project folders, particularly files with suspicious names or in unusual locations. Log access to terminal escape sequences and OSC protocol handlers if your terminal multiplexer or logging solution supports it. In security monitoring, look for evidence of file materialization without corresponding user file operations. Endpoint detection and response tools should flag unauthorized file writes originating from Warp processes. Additionally, review recent command history and SSH sessions to identify exposure to potentially compromised sources.

Why prioritize this

Despite not appearing on CISA's KEV list, this vulnerability merits urgent attention due to its intersection of high CVSS score, trivial exploitability, and deep integration into developer workflows. The attack surface is broad—any developer running Warp and interacting with untrusted remote output is at risk. The lack of user confirmation makes this especially dangerous in fast-paced development environments where users routinely pipe commands and scripts without scrutiny. Organizations should prioritize patching ahead of active exploitation.

Risk score, explained

The CVSS 3.1 score of 8.8 reflects: network-adjacent attack vector (AV:N), low attack complexity (AC:L), no privilege requirement (PR:N), and user interaction required (UI:R). The impact ratings are uniformly high: confidential data can be exfiltrated via written files, system integrity is compromised by arbitrary file creation, and availability can be affected by destructive file operations. The score appropriately captures the severity while acknowledging that user interaction (running a command or clicking a link) is a prerequisite.

Frequently asked questions