OS Command Injection in Warp (CVE-2026-48732)
Summary
OS command injection in Warp (CVE-2026-48732). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.2026.05.06.15.42.stable or later.
Original description
The description as published by the source.
Warp is an agentic development environment. From 0.2023.03.21.08.02.stable_00 until 0.2026.05.06.15.42.stable_01, Warp contains a command injection issue in the legacy SSH background command path. Warp used the remote working directory reported by the session when building helper commands for SSH-backed metadata collection. A remote host, repository, or directory name controlled by an attacker could cause that helper command to execute additional shell syntax on the remote host as the victim's authenticated SSH account. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48732 has been found in Warp.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade Warp to 0.2026.05.06.15.42.stable or later.
If unsure, ask your IT team or search "Warp CVE-2026-48732" on the vendor's site.
CVE-2026-48732 (Warp) — CWE-78 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.2026.05.06.15.42.stable — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
OS command injection (CWE-78) exists in Warp.
Check the vendor advisory for the affected versions of Warp.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 0.2026.05.06.15.42.stable.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Warp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Warp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Warpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Warp to 0.2026.05.06.15.42.stableステージング環境で 0.2026.05.06.15.42.stable に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com