JetBrains WebStorm
7 published vulnerabilities name this product.
As the CNAs write it in their CVE records (vendor and product); the versions are theirs.
| CVE | Vulnerable versions | Title | Severity | Published | EPSS | Exploitation |
|---|---|---|---|---|---|---|
| CVE-2026-118696 | 2026.2 – < 2026.2.4 ; 2026.1 – < 2026.1.5.1 ; < 2025.3.6.2 | In JetBrains IntelliJ IDEA, PyCharm, PhpStorm, RubyMine and WebStorm before 2026.3, 2026.2.4, 2026.1.5.1, and 2025.3.6.2; GoLand before 2026 | HIGH 8.0 | 0.3 % | ||
| CVE-2026-64807 | < 2026.2 | In JetBrains WebStorm before 2026.2 arbitrary code execution was possible via a project-supplied linter configuration | HIGH 7.8 | 0.2 % | ||
| CVE-2026-64806 | < 2026.2 | In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via the configured Node.js interpret | HIGH 8.4 | 0.2 % | ||
| CVE-2026-64805 | < 2026.2 | In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via project-local package-manager to | HIGH 8.4 | 0.2 % | ||
| CVE-2026-64804 | < 2026.2 | In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via project-local linter tooling | HIGH 8.4 | 0.2 % | ||
| CVE-2024-52555 | < 2024.3 | In JetBrains WebStorm before 2024.3 code execution in Untrusted Project mode was possible via type definitions installer script | HIGH 7.8 | 0.1 % | ||
| CVE-2024-37051 | | GitHub access token could be exposed to third-party sites in JetBrains IDEs after version 2023.1 and less than: IntelliJ IDEA 2023.1.7, 2023 | CRITICAL 9.3 | 4.9 % |