JetBrains Phpstorm vulnerabilities

6 CVEs affecting JetBrains Phpstorm, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2026-64809, published 2026-07-23.

Highest priority

Known exploited (CISA KEV) first, then by EPSS exploit probability.

CVE-2024-37051, published 2024-06-10. High severity, CVSS 7.5. EPSS: 4.9% chance of exploitation in the next 30 days. 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; Aqua 2024.1.2; CLion…
CVE-2021-45977, published 2022-02-25. Critical severity, CVSS 9.8. EPSS: 1.1% chance of exploitation in the next 30 days. 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 2021.3.1 Preview,…
CVE-2021-25764, published 2021-03-18. Medium severity, CVSS 5.3. EPSS: 0.8% chance of exploitation in the next 30 days. In JetBrains PhpStorm before 2020.3, source code could be added to debug logs.
CVE-2026-64809, published 2026-07-23. High severity, CVSS 8.4. EPSS: 0.2% chance of exploitation in the next 30 days. In JetBrains PhpStorm before 2026.2 arbitrary code execution was possible before granting project trust via the configured interpreter
CVE-2026-64808, published 2026-07-23. High severity, CVSS 8.4. EPSS: 0.2% chance of exploitation in the next 30 days. In JetBrains PhpStorm before 2026.2 arbitrary code execution was possible before granting project trust via project tooling
CVE-2022-48435, published 2023-04-04. Low severity, CVSS 3.3. EPSS: 0.2% chance of exploitation in the next 30 days. In JetBrains PhpStorm before 2023.1 source code could be logged in the local idea.log file