Is CVE-2026-64806 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-64806 being exploited in the wild.

How severe is CVE-2026-64806?

High severity, with a CVSS score of 8.4, published 23 July 2026.

Which products and versions are affected?

Jetbrains WebStorm before 2026.2.

Is there a fix for CVE-2026-64806?

A patch was published on 2026-07-23: Fixed in WebStorm version 2026.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-64806 attacked?

It is attacked with local access, in a network appliance.

Am I affected by CVE-2026-64806?

Check whether you run Jetbrains WebStorm 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.

CVE-2026-64806: JetBrains WebStorm arbitrary code execution via Node.js interpreter

CVE-2026-64806 · Severity: high · CVSS 8.4 · Published 2026-07-23

JetBrains WebStorm, a popular development environment for JavaScript, contained a security flaw that allowed malicious code to run automatically when a project was opened. Typically, the software asks for user permission before trusting a new project, but this vulnerability bypassed that safeguard by using the configured Node.js interpreter. An attacker could use this to gain full control over a developer's workstation simply by convincing them to open a malicious project folder.

Technologies: Jetbrains WebStorm. Vendors: Jetbrains.

Quick answers

Is CVE-2026-64806 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-64806 being exploited in the wild.
How severe is CVE-2026-64806?: High severity, with a CVSS score of 8.4, published 23 July 2026.
Which products and versions are affected?: Jetbrains WebStorm before 2026.2.
Is there a fix for CVE-2026-64806?: A patch was published on 2026-07-23: Fixed in WebStorm version 2026.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-64806 attacked?: It is attacked with local access, in a network appliance.
Am I affected by CVE-2026-64806?: Check whether you run Jetbrains WebStorm 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 WebStorm versions prior to 2026.2 allowed for arbitrary code execution by exploiting the Node.js interpreter configuration. The flaw stems from the inclusion of functionality from an untrusted control sphere (CWE-829), where the IDE would execute code via the configured Node.js interpreter before the user had explicitly granted 'Project Trust'. An attacker could exploit this by providing a malicious project that triggers execution upon being opened in the IDE. This bypasses the security sandbox intended to protect users from untrusted code. The issue is resolved in version 2026.2.

Affected products

JetBrains WebStorm before 2026.2

Timeline

2026-07-23: advisory: CVE-2026-64806 published by JetBrains
2026-07-23: patched: Fixed in WebStorm version 2026.2

References

https://www.jetbrains.com/privacy-security/issues-fixed/

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.