JetBrains / WebStorm
9 CVEs
| CVE ID | Description | Severity | CVSS | Published |
|---|---|---|---|---|
| CVE-2026-64807 | In JetBrains WebStorm before 2026.2 arbitrary code execution was possible via a project-supplied linter configuration | HIGH | 7.8 | Jul 23, 2026 |
| CVE-2026-64806 | In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via the configured Node.js interpreter | HIGH | 8.4 | Jul 23, 2026 |
| CVE-2026-64805 | In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via project-local package-manager tooling | HIGH | 8.4 | Jul 23, 2026 |
| CVE-2026-64804 | In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via project-local linter tooling | HIGH | 8.4 | Jul 23, 2026 |
| CVE-2024-52555 | In JetBrains WebStorm before 2024.3 code execution in Untrusted Project mode was possible via type definitions installer script | HIGH | 7.8 | Nov 15, 2024 |
| 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.2.7, 2023.3.7, 202… | CRITICAL | 9.3 | Jun 10, 2024 |
| CVE-2021-45977 | 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 202… | CRITICAL | 9.8 | Feb 25, 2022 |
| CVE-2021-31897 | In JetBrains WebStorm before 2021.1, code execution without user confirmation was possible for untrusted projects. | CRITICAL | 9.8 | May 11, 2021 |
| CVE-2021-31898 | In JetBrains WebStorm before 2021.1, HTTP requests were used instead of HTTPS. | HIGH | 7.5 | May 11, 2021 |
Showing 1 to 9 of 9 CVEs