Loading vulnerability…
CVE-2026-64805 is an arbitrary code execution vulnerability affecting JetBrains WebStorm versions prior to 2026.2. The flaw allows code execution before the user grants trust to an opened project, undermining the intended project trust security boundary. The vulnerable attack path involves project-local package-manager tooling, where a malicious project can cause execution of attacker-controlled code during project opening or initialization before trust confirmation is obtained. The issue is classified as CWE-829, indicating inclusion or use of functionality from an untrusted control sphere.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A JetBrains vulnerability listed among the patched issues; the article does not further describe the flaw beyond its CWE and fixed version.
An arbitrary code execution vulnerability in JetBrains WebStorm before version 2026.2 that could be triggered prior to granting project trust through project-local package-manager tooling.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.