CVE-2026-64808 json
In JetBrains PhpStorm before 2026.2 arbitrary code execution was possible before granting project trust via project tooling
published 3mo ago modified 18d ago also EUVD-2026-48233
- cvss
- 8.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
In JetBrains PhpStorm before 2026.2 arbitrary code execution was possible before granting project trust via project tooling
Patch / fix
- JetBrains PhpStorm 2026.2
Is CVE-2026-64808 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 3mo ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.4 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- JetBrains PhpStorm
Classification
- Weakness
-
- CWE-829 Inclusion of Functionality from Untrusted Control Sphere
References
-
jetbrains.com
/privacy-security/issues-fixed/
vendor-advisory
Sources
- CVE List CVE-2026-64808
- NVD CVE-2026-64808
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.