CVE-2026-54699

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% 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
7.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.7Exploit: 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.2024.03.12.08.02.stable_01 until 0.2026.05.06.15.42.stable_01, Warp contains an OS command injection vulnerability in the WSL URL-opening fallback. When Warp is running under WSL and cannot open a URL through wslview, it falls back to a Windows command processor path. A URL controlled through terminal output can reach that fallback when the user opens the link. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01.

CVSS v3
7.7
EG Score
7.7(medium)
EPSS
35.1%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 25, 2026

Advisory Details (2)

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

OS command injection when opening terminal links from WSL · Advisory · warpdotdev/warp · GitHub

https://github.com/warpdotdev/warp/security/advisories/GHSA-xmw3-wj6r-48m4
github_commit Patch Available

commit c66cff48afba (warpdotdev/warp)

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

https://github.com/warpdotdev/warp/commit/c66cff48afba73bb1f26f82e5d524018bacb748e

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 61× 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-12 05:46 UTCEPSS rescore
  2. 2026-07-11 22:42 UTCEG score recompute
  3. 2026-07-11 10:20 UTCEG score recompute
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-10 21:58 UTCEG score recompute
  7. 2026-07-10 09:36 UTCEG score recompute
  8. 2026-07-09 21:07 UTCEG score recompute
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 08:45 UTCEG score recompute
  12. 2026-07-08 20:21 UTCEG score recompute
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-08 07:57 UTCEG score recompute
  16. 2026-07-07 19:35 UTCEG score recompute
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-07 07:00 UTCEG score recompute
  20. 2026-07-06 18:39 UTCEG score recompute
  21. 2026-07-06 16:27 UTCEPSS rescore
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 06:16 UTCEG score recompute
  24. 2026-07-06 02:23 UTCEPSS rescore
  25. 2026-07-06 02:23 UTCEPSS rescore
Show 36 more
  1. 2026-07-05 17:40 UTCEG score recompute
  2. 2026-07-05 05:18 UTCEG score recompute
  3. 2026-07-05 02:31 UTCEPSS rescore
  4. 2026-07-05 02:30 UTCEPSS rescore
  5. 2026-07-04 16:56 UTCEG score recompute
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-04 04:34 UTCEG score recompute
  9. 2026-07-03 16:12 UTCEG score recompute
  10. 2026-07-03 03:50 UTCEG score recompute
  11. 2026-07-02 15:24 UTCEG score recompute
  12. 2026-07-02 03:00 UTCEG score recompute
  13. 2026-07-01 15:07 UTCEPSS rescore
  14. 2026-07-01 14:38 UTCEG score recompute
  15. 2026-07-01 02:17 UTCEG score recompute
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 13:55 UTCEG score recompute
  18. 2026-06-30 01:31 UTCEG score recompute
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-29 13:10 UTCEG score recompute
  22. 2026-06-29 00:48 UTCEG score recompute
  23. 2026-06-28 14:07 UTCEPSS rescore
  24. 2026-06-28 12:27 UTCEG score recompute
  25. 2026-06-28 04:56 UTCEPSS rescore
  26. 2026-06-28 04:56 UTCEPSS rescore
  27. 2026-06-28 00:05 UTCEG score recompute
  28. 2026-06-27 11:43 UTCEG score recompute
  29. 2026-06-27 03:08 UTCEPSS rescore
  30. 2026-06-26 23:21 UTCEG score recompute
  31. 2026-06-26 11:00 UTCEG score recompute
  32. 2026-06-25 20:51 UTCEG score recompute
  33. 2026-06-25 13:49 UTCEPSS rescore
  34. 2026-06-25 08:29 UTCEG score recompute
  35. 2026-06-24 20:08 UTCEG score recompute
  36. 2026-06-24 20:03 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54699?
CVE-2026-54699 is a high vulnerability published on June 24, 2026. Warp is an agentic development environment. From 0.2024.03.12.08.02.stable01 until 0.2026.05.06.15.42.stable01, Warp contains an OS command injection vulnerability in the WSL URL-opening fallback. When Warp is running under WSL and cannot open a URL through wslview, it falls back to a Windows…
When was CVE-2026-54699 disclosed?
CVE-2026-54699 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-54699 actively exploited?
CVE-2026-54699 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54699?
CVE-2026-54699 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-54699?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54699, 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-54699

Explore →

Is Your Infrastructure Affected by CVE-2026-54699?

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

Start Free Scan →Browse All CVEs