Security readout for executives and security teams
Plain-English summary
WebStorm versions before 2026.2 could run code from project-local package-manager tooling before the user approved the project as trusted. A malicious or compromised project could therefore bypass an important safety boundary and affect the developer’s workstation, files, credentials, or availability.
Executive priority
Treat this as a high-priority developer-endpoint update. Expedite remediation where WebStorm users handle external repositories or possess valuable credentials and production access. Broader emergency response is not supported by current evidence because active exploitation is unconfirmed.
Technical view
CVE-2026-64805 is a CWE-829 trust-boundary flaw with CVSS 3.1 score 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The supplied record describes arbitrary code execution through project-local package-manager tooling before project trust is granted. It does not document the precise trigger or implementation details.
Likely exposure
Exposure is most likely where WebStorm before 2026.2 processes untrusted, attacker-controlled, or compromised projects using project-local package-manager tooling. Developer systems holding source code, tokens, signing material, or production access warrant priority. The machine-readable affected entry is incomplete, so exact version applicability should be confirmed with JetBrains.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires local project content or tooling to reach WebStorm, but the stated vector indicates no privileges or additional user interaction after that condition. No public exploit evidence is provided.
Researcher notes
The central issue is execution before project-trust approval through project-local package-manager tooling. CWE-829 indicates unsafe inclusion of functionality from an untrusted control sphere. The affected-version metadata contains an anomalous “0” entry with default status unaffected, conflicting with the title’s “before 2026.2” boundary; validate against JetBrains before making exhaustive exposure claims.
Mitigation direction
- Upgrade WebStorm to version 2026.2 or later, subject to JetBrains guidance.
- Prioritize developer workstations that open external, downloaded, forked, or contributor-supplied projects.
- Until upgraded, avoid opening untrusted projects in affected WebStorm installations.
- Review JetBrains security guidance for additional mitigations or version-specific instructions.
Validation and detection
- Inventory installed WebStorm versions and identify installations earlier than 2026.2.
- Confirm upgraded installations report WebStorm 2026.2 or later.
- Identify developers who recently opened untrusted or externally sourced projects.
- Review endpoint telemetry for unusual child processes or credential access associated with WebStorm.
- Verify exact affected-version boundaries against the current JetBrains advisory.
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-64805 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.