Security readout for executives and security teams
Plain-English summary
A malicious or compromised WebStorm project could supply a linter configuration that causes code to run when a developer interacts with the project. Successful exploitation could expose source code, alter files, steal accessible credentials, or disrupt the workstation. WebStorm releases before 2026.2 are affected.
Executive priority
Treat this as a high-priority developer-workstation update. Accelerate remediation where teams review outside code or handle sensitive repositories and credentials. Broader emergency response is not supported by the current evidence because active exploitation has not been established.
Technical view
CVE-2026-64807 is a CWE-829 trust-boundary flaw in WebStorm’s handling of project-supplied linter configuration. It permits arbitrary code execution with local attack proximity and required user interaction. CVSS 3.1 rates it 7.8: AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
Likely exposure
Exposure is most likely among developers using WebStorm versions before 2026.2 who open untrusted, externally contributed, or compromised projects. Risk also exists where trusted repositories can be modified through compromised accounts or dependencies. The sources do not identify particular operating systems or linter products.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation or a public exploit. Exploitation requires user interaction with a project containing attacker-controlled linter configuration; the precise triggering interaction is not documented in the supplied sources.
Researcher notes
The public description is brief and does not identify the affected linter, configuration format, execution path, or exact trigger. Researchers should avoid assuming automatic execution merely from opening a project. Version scope is stated as WebStorm before 2026.2; the bundle’s structured affected-version value is incomplete and should not override that statement.
Mitigation direction
- Upgrade WebStorm to version 2026.2 or later after confirming JetBrains guidance.
- Prioritize developers who routinely open external repositories, samples, pull requests, or customer-supplied projects.
- Until upgraded, avoid opening untrusted projects and treat project linter configuration as executable-risk content.
- Review JetBrains security guidance for any additional product-specific precautions.
Validation and detection
- Inventory installed WebStorm versions and identify every installation earlier than 2026.2.
- Confirm upgraded endpoints report WebStorm 2026.2 or later.
- Review repositories for unexpected or recently changed project-supplied linter configuration.
- Check affected developer endpoints for suspicious activity following interaction with untrusted projects.
- Verify software-management reporting covers unmanaged developer workstations.
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-64807 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
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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:R/S:U/C:H/I:H/A:H1.85.9JetBrainsVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.