Security readout for executives and security teams
Plain-English summary
WebStorm versions before 2026.2 could run arbitrary code through the configured Node.js interpreter before a project was marked trusted. A malicious or compromised project could therefore undermine WebStorm’s trust boundary, potentially exposing developer credentials, source code, and the workstation.
Executive priority
Treat this as a high-priority developer-workstation update. Accelerate WebStorm 2026.2 deployment and investigate exposed endpoints because developer systems commonly hold valuable code and credentials. The bundle provides no evidence of active exploitation, so emergency incident status is not justified without additional indicators.
Technical view
CVE-2026-64806 is a local arbitrary-code-execution vulnerability classified as CWE-829. It affects WebStorm before 2026.2 and involves the configured Node.js interpreter executing code before project trust approval. CVSS 3.1 rates it 8.4, with low complexity, no privileges, and high confidentiality, integrity, and availability impact.
Likely exposure
Prioritize developer endpoints running WebStorm versions earlier than 2026.2, particularly where users open projects from external or uncertain sources. The supplied affected-product metadata contains an unclear version value of “0” and a default status of unaffected, so confirm precise applicability through JetBrains guidance.
Exploitation context
The bundle does not establish active exploitation, and the CVE is not listed as KEV. Exploitation requires local access according to the CVSS vector. The sources do not explain project-delivery mechanisms, exact interpreter behavior, proof-of-concept availability, or observed attacks.
Researcher notes
Public details are limited to the affected boundary, interpreter-related trust bypass, CWE-829, and CVSS vector. The supplied version metadata is internally unclear, and no root cause, advisory identifier, affected platform distinctions, detection indicators, or technical mitigation beyond the 2026.2 boundary is provided.
Mitigation direction
- Upgrade WebStorm to version 2026.2 or later.
- Confirm the installed build against JetBrains security guidance.
- Avoid opening untrusted projects with older WebStorm versions.
- Review configured Node.js interpreters and remove unexpected configurations.
- Apply additional vendor guidance if JetBrains publishes it.
Validation and detection
- Inventory WebStorm versions across developer endpoints.
- Verify upgraded installations report version 2026.2 or later.
- Identify systems that recently opened externally sourced projects.
- Review Node.js interpreter configurations for unexpected paths or changes.
- Examine endpoint telemetry for unexpected WebStorm-initiated Node.js execution.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-829: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-64806 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9JetBrainsVulnerability scoring details
Base CVSS 3.1 score
8.4HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.jetbrains.com/privacy-security/issues-fixed/CVE reference, JetBrains
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.