Quick answers
- Is CVE-2026-48719 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48719 being exploited in the wild.
- How severe is CVE-2026-48719?
- High severity, with a CVSS score of 8, published 24 June 2026.
- Which products and versions are affected?
- warpdotdev Warp >= 0.2025.08.06.08.12.stable_00, < 0.2026.05.06.15.42.stable_01.
- Is there a fix for CVE-2026-48719?
- A patch was published on 2026-05-06: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48719 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48719?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A command injection vulnerability exists in Warp's prompt branch selector component due to improper neutralization of special elements in Git branch names. An attacker with the ability to publish branches to a repository can craft a branch name containing shell metacharacters. When a victim opens the repository in Warp and selects the malicious branch via the UI, the crafted name is interpreted by the victim's local shell. This allows for Remote Code Execution (RCE) with the privileges of the local user. The fix involves replacing command strings with typed command intents and implementing proper shell argument quoting (shell_quote_arg) before execution.
Affected products
- warpdotdev Warp >= 0.2025.08.06.08.12.stable_00, < 0.2026.05.06.15.42.stable_01
Timeline
- 2026-05-06: patched: Fix committed to repository
- 2026-06-09: advisory: GitHub Security Advisory published
- 2026-06-24: disclosed: CVE published to NVD