CVE-2026-48719

HIGHPre-NVD 8.08.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 43% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Warp is an agentic development environment. From 0.2025.08.06.08.12.stable_00 until 0.2026.05.06.15.42.stable_01, Warp contains a command injection in the prompt branch selector. A user who can publish a branch to a Git repository opened in Warp can cause a crafted branch name to be interpreted by the victim's shell if the victim selects that branch from the UI. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01.

CVSS v3
8.0
EG Score
8.0(medium)
EPSS
57.2%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 24, 2026
Patch available. Sources: github, github_commit.
github Patch Available

Branch selector command injection via Git branch names · Advisory · warpdotdev/warp · GitHub

https://github.com/warpdotdev/warp/security/advisories/GHSA-hgvx-4xvm-39pw
github_commit Patch Available

commit 4295ec08d019 (warpdotdev/warp)

Patch available: warpdotdev/warp v0.2026.06.09.19.54.dev_00 (contains commit 4295ec08d019)

https://github.com/warpdotdev/warp/commit/4295ec08d01912fe355351547e541277f29288cd

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 64× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 01:48 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 13:06 UTCEG score recompute
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 00:24 UTCEG score recompute
  6. 2026-07-14 11:41 UTCEG score recompute
  7. 2026-07-13 22:56 UTCEG score recompute
  8. 2026-07-13 22:30 UTCEPSS rescore
  9. 2026-07-13 10:14 UTCEG score recompute
  10. 2026-07-13 06:13 UTCEPSS rescore
  11. 2026-07-12 21:19 UTCEG score recompute
  12. 2026-07-12 08:20 UTCEG score recompute
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-11 19:38 UTCEG score recompute
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-11 06:56 UTCEG score recompute
  17. 2026-07-10 18:12 UTCEG score recompute
  18. 2026-07-10 05:24 UTCEG score recompute
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 16:43 UTCEG score recompute
  21. 2026-07-09 03:58 UTCEG score recompute
  22. 2026-07-08 15:17 UTCEG score recompute
  23. 2026-07-08 15:16 UTCEPSS rescore
  24. 2026-07-08 02:34 UTCEG score recompute
  25. 2026-07-07 13:50 UTCEG score recompute
Show 39 more
  1. 2026-07-07 13:46 UTCEPSS rescore
  2. 2026-07-07 01:09 UTCEG score recompute
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 12:27 UTCEG score recompute
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 23:43 UTCEG score recompute
  7. 2026-07-05 11:01 UTCEG score recompute
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 22:19 UTCEG score recompute
  10. 2026-07-04 09:37 UTCEG score recompute
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 20:55 UTCEG score recompute
  13. 2026-07-03 08:14 UTCEG score recompute
  14. 2026-07-02 19:32 UTCEG score recompute
  15. 2026-07-02 06:49 UTCEG score recompute
  16. 2026-07-01 18:07 UTCEG score recompute
  17. 2026-07-01 15:07 UTCEPSS rescore
  18. 2026-07-01 05:25 UTCEG score recompute
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-30 16:43 UTCEG score recompute
  21. 2026-06-30 04:01 UTCEG score recompute
  22. 2026-06-29 15:19 UTCEG score recompute
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 02:29 UTCEG score recompute
  26. 2026-06-28 14:07 UTCEPSS rescore
  27. 2026-06-28 13:47 UTCEG score recompute
  28. 2026-06-28 04:56 UTCEPSS rescore
  29. 2026-06-28 04:56 UTCEPSS rescore
  30. 2026-06-28 01:06 UTCEG score recompute
  31. 2026-06-27 12:24 UTCEG score recompute
  32. 2026-06-27 03:08 UTCEPSS rescore
  33. 2026-06-26 23:41 UTCEG score recompute
  34. 2026-06-26 11:00 UTCEG score recompute
  35. 2026-06-25 21:33 UTCEG score recompute
  36. 2026-06-25 13:49 UTCEPSS rescore
  37. 2026-06-25 08:50 UTCEG score recompute
  38. 2026-06-24 20:09 UTCEG score recompute
  39. 2026-06-24 20:03 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48719?
CVE-2026-48719 is a high vulnerability published on June 24, 2026. Warp is an agentic development environment. From 0.2025.08.06.08.12.stable00 until 0.2026.05.06.15.42.stable01, Warp contains a command injection in the prompt branch selector. A user who can publish a branch to a Git repository opened in Warp can cause a crafted branch name to be interpreted by…
When was CVE-2026-48719 disclosed?
CVE-2026-48719 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48719 actively exploited?
CVE-2026-48719 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 57.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48719?
CVE-2026-48719 has a CVSS v3 base score of 8.0 (NVD).
How do I remediate CVE-2026-48719?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48719, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-48719

Explore →

Is Your Infrastructure Affected by CVE-2026-48719?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs