Security readout for executives and security teams
Plain-English summary
A WebStorm flaw could let code associated with a project run before the IDE asks whether the project should be trusted. A malicious or compromised project could therefore affect the developer’s machine. The supplied record rates the issue high and identifies WebStorm versions before 2026.2 as vulnerable.
Executive priority
Prioritize prompt developer-endpoint inventory and upgrading because successful exploitation could fully compromise sensitive source code, credentials, and workstation availability. Apply temporary restrictions to untrusted projects where immediate updating is not possible.
Technical view
WebStorm processed project-local linter tooling before project trust was granted, enabling arbitrary code execution. The record assigns CWE-829 and CVSS 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating low-complexity local exploitation with potentially severe confidentiality, integrity, and availability impact.
Likely exposure
Organizations may be exposed where developers run WebStorm earlier than 2026.2 and handle projects containing project-local linter tooling. Untrusted or compromised projects present the clearest risk. The structured affected-version data is incomplete, so confirm exact applicability with JetBrains.
Exploitation context
The supplied bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or public exploit availability. This does not prove exploitation has never occurred.
Researcher notes
The title and description identify WebStorm before 2026.2, but the structured affected entry lists only version “0” with a default unaffected status. Treat automated version matching cautiously and confirm with JetBrains. No root cause detail, indicators, exploit evidence, or release-specific mitigation beyond the fixed-version boundary is supplied.
Mitigation direction
- Upgrade affected WebStorm installations to version 2026.2 or later, following JetBrains guidance.
- Until upgraded, avoid opening untrusted or externally sourced projects in affected WebStorm versions.
- Review JetBrains security guidance for additional mitigations or release-specific instructions.
Validation and detection
- Inventory WebStorm installations and identify versions earlier than 2026.2.
- Confirm updated endpoints report WebStorm 2026.2 or later.
- Identify affected users who recently opened untrusted projects using project-local linter tooling.
- Review endpoint telemetry around affected WebStorm use; the source bundle supplies no indicators of compromise.
- In a controlled test, confirm project-local lint tooling cannot execute before project trust.
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-64804 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.