Warp versions from 0.2025.03.05.08.02.stable_00 until 0.2026.05.06.15.42.stable_01 accept non-inline OSC 1337;File payloads embedded in terminal output and write the decoded data to local files without any confirmation. The lack of bounds and path validation allows an attacker to overwrite any file that the Warp process can write to, including configuration files or executable scripts. This could enable persistence by substituting startup or system scripts, or if an executable is written, could lead to code execution.

The vulnerable product is Warp by warpdotdev. All releases between 0.2025.03.05.08.02.stable_00 and 0.2026.05.06.15.42.stable_01 are impacted. The issue was patched in the release 0.2026.05.06.15.42.stable_01, which adds a confirmation step and bounds checking for OSC 1337 payloads.

With a CVSS score of 8.8, the vulnerability is considered high severity. The EPSS score is not provided, but the absence of an official KEV listing suggests no widespread exploitation yet. The likely attack vector is remote via an SSH session where an attacker controls terminal output; the Warp application would then materialize the payload as a local file. Because the vulnerability permits arbitrary file overwrite, an attacker could gain persistence or elevate privileges, especially if the written file resides in a directory executed on boot or by a privileged user.