Quick answers
- Is CVE-2026-64809 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64809 being exploited in the wild.
- How severe is CVE-2026-64809?
- High severity, with a CVSS score of 8.4, published 23 July 2026.
- Which products and versions are affected?
- Jetbrains PhpStorm before 2026.2.
- Is there a fix for CVE-2026-64809?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-64809 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-64809?
- Check whether you run Jetbrains PhpStorm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability in JetBrains PhpStorm versions prior to 2026.2 allowed for arbitrary code execution due to improper handling of untrusted control spheres (CWE-829). The flaw exists in the way the IDE interacts with configured interpreters when a project is first opened. Specifically, the application could execute code through the interpreter before the 'Project Trust' security mechanism had a chance to intervene and block unauthorized actions. An attacker could exploit this by providing a malicious project configuration that triggers code execution upon being loaded by the IDE. This issue has been resolved in version 2026.2.
Affected products
- JetBrains PhpStorm before 2026.2
Timeline
- 2026-07-23: disclosed
- 2026-07-23: advisory