CVE-2026-64807
Published Jul 23, 2026In JetBrains WebStorm before 2026.2 arbitrary code execution was possible via a project-supplied linter configuration
- evidence mentions
- 1
- Buzz score
- 11.9
Vendor/product archive
9 CVEs tagged to jetbrains / webstorm — 3 Critical, 5 High, 1 Medium, 0 Low, 0 Unrated.
In JetBrains WebStorm before 2026.2 arbitrary code execution was possible via a project-supplied linter configuration
In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via the configured Node.js interpreter
In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via project-local package-manager tooling
In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via project-local linter tooling
In JetBrains WebStorm before 2024.3 code execution in Untrusted Project mode was possible via type definitions installer script
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.2.7, 2023.3.7, 2024.1.3, 2024.2 EAP3;…
JetBrains IntelliJ IDEA 2021.3.1 Preview, IntelliJ IDEA 2021.3.1 RC, PyCharm Professional 2021.3.1 RC, GoLand 2021.3.1, PhpStorm 2021.3.1 Preview, PhpStorm 2021.3.1 RC, RubyMine 2…
In JetBrains WebStorm before 2021.1, HTTP requests were used instead of HTTPS.
In JetBrains WebStorm before 2021.1, code execution without user confirmation was possible for untrusted projects.