warpdotdev warp up to 0.2023.10.24.08.03/0.2026.05.06.15.42 Markdown input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.67 |
Summary
A vulnerability categorized as critical has been discovered in warpdotdev warp up to 0.2023.10.24.08.03/0.2026.05.06.15.42. This impacts an unknown function of the component Markdown Handler. Such manipulation leads to input validation. This vulnerability is traded as CVE-2026-48704. The attack may be launched remotely. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in warpdotdev warp up to 0.2023.10.24.08.03/0.2026.05.06.15.42 and classified as critical. Affected by this issue is an unknown functionality of the component Markdown Handler. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Warp is an agentic development environment. From 0.2023.10.24.08.03.stable_00 until 0.2026.05.06.15.42.stable_01, Warp may open executable local files through the operating system default file handler. A malicious Markdown document or project can contain a local-file link that appears as normal rendered content. If a user opens the Markdown in Warp and clicks the link, affected builds may route the resolved local file to a platform file opener instead of limiting the action to safe viewer/editor targets. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01.
The advisory is available at github.com. This vulnerability is handled as CVE-2026-48704 since 05/22/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available.
Upgrading to version 0.2026.05.13.09.15.stable_01 eliminates this vulnerability. Applying the patch 7f0c4dd2322198f1b39890f8e6bcdc606c6a3c74 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
- 0.2023.10.24.08.03
- 0.2026.05.06.15.0
- 0.2026.05.06.15.1
- 0.2026.05.06.15.2
- 0.2026.05.06.15.3
- 0.2026.05.06.15.4
- 0.2026.05.06.15.5
- 0.2026.05.06.15.6
- 0.2026.05.06.15.7
- 0.2026.05.06.15.8
- 0.2026.05.06.15.9
- 0.2026.05.06.15.10
- 0.2026.05.06.15.11
- 0.2026.05.06.15.12
- 0.2026.05.06.15.13
- 0.2026.05.06.15.14
- 0.2026.05.06.15.15
- 0.2026.05.06.15.16
- 0.2026.05.06.15.17
- 0.2026.05.06.15.18
- 0.2026.05.06.15.19
- 0.2026.05.06.15.20
- 0.2026.05.06.15.21
- 0.2026.05.06.15.22
- 0.2026.05.06.15.23
- 0.2026.05.06.15.24
- 0.2026.05.06.15.25
- 0.2026.05.06.15.26
- 0.2026.05.06.15.27
- 0.2026.05.06.15.28
- 0.2026.05.06.15.29
- 0.2026.05.06.15.30
- 0.2026.05.06.15.31
- 0.2026.05.06.15.32
- 0.2026.05.06.15.33
- 0.2026.05.06.15.34
- 0.2026.05.06.15.35
- 0.2026.05.06.15.36
- 0.2026.05.06.15.37
- 0.2026.05.06.15.38
- 0.2026.05.06.15.39
- 0.2026.05.06.15.40
- 0.2026.05.06.15.41
- 0.2026.05.06.15.42
License
Website
- Product: https://github.com/warpdotdev/warp/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.8
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: warp 0.2026.05.13.09.15.stable_01
Patch: 7f0c4dd2322198f1b39890f8e6bcdc606c6a3c74
Timeline
05/22/2026 CVE reserved06/24/2026 Advisory disclosed
06/24/2026 VulDB entry created
06/24/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-589x-4mxh-jcrf
Status: Confirmed
CVE: CVE-2026-48704 (🔒)
GCVE (CVE): GCVE-0-2026-48704
GCVE (VulDB): GCVE-100-373514
Entry
Created: 06/24/2026 21:29Changes: 06/24/2026 21:29 (66)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.