CVE-2026-64809
Arbitrary code execution in PhpStorm before project trust via configured interpreter
Is CVE-2026-64809 being exploited?
Not confirmed. CVE-2026-64809 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.19% probability of exploitation in the next 30 days.
How severe is CVE-2026-64809?
CVE-2026-64809 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64809?
Yes. A fix has been recorded for CVE-2026-64809. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64809 affect?
CVE-2026-64809 affects JetBrains PhpStorm < 2026.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64809?
Upgrade to PhpStorm 2026.2+ and avoid opening untrusted projects
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Allows attackers to execute arbitrary code on a developer host when opening an untrusted project using the configured interpreter before trust is granted.
Patch when possible
- affected< 2026.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.