Skip to main content

JetBrains WebStorm CVE-2026-64804

| EUVDEUVD-2026-48229 HIGH
Inclusion of Functionality from Untrusted Control Sphere (CWE-829)
2026-07-23 cve@jetbrains.com GHSA-x88m-wx27-x7m2
8.4
CVSS 3.1 · Vendor: jetbrains
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft repo with malicious project-local linter
  2. Delivery
    Lure developer to clone and open in WebStorm
  3. Exploit
    IDE auto-invokes linter before trust granted
  4. Execution
    Attacker code executes with developer privileges
  5. Impact
    Compromise dev workstation and credentials

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V15 - Secure Coding and Architecture Trusted source inclusion only
Exploitation Conditions

Exploitation requires a victim developer to open or import an attacker-crafted project in WebStorm that ships a malicious project-local linter (e.g., ESLint/TSLint) binary and/or configuration; the code runs during the pre-trust automatic tooling invocation, before the user clicks 'Trust Project'. Limiting factors: the attacker must deliver the hostile repository and induce the target to open it locally (AV:L), the affected build must be earlier than WebStorm 2026.2, and the IDE's linter integration must engage the project-local tooling. The NVD vector's UI:N understates the practical need for the user to open the project; the exploit does not work over the network without that local action.

Impact

The NVD CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.4) rates this High with full CIA impact but a LOCAL attack vector and, notably, UI:N - which conflicts with the description's premise that a victim must open/import a malicious project. That UI:N is likely optimistic: realistically some user interaction (opening the project) is required, which lowers real-world likelihood versus a purely passive local flaw - verify with vendor. No EPSS score, KEV listing, or POC was provided, so there is no public exploit identified at time of analysis and no evidence of active exploitation. Net: a genuinely high-impact code-execution issue for developer workstations, but exploitation depends on social engineering a developer into opening a hostile repository, making it a targeted supply-chain/developer-trust risk rather than a mass-exploitable network threat.

Exploit ScenarioDerived

An attacker publishes a repository (e.g., an npm package fork, coding challenge, or job-application starter kit) containing a malicious project-local linter binary and configuration. When a developer clones and opens it in a vulnerable WebStorm, the IDE invokes the linter tooling before showing/honoring the trust prompt, executing the attacker's code with the developer's privileges. No public POC is currently identified, and the local attack vector means the attacker relies on luring the victim into opening the project.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 23, 2026

Arbitrary code execution in JetBrains WebStorm before 2026.2 allows a malicious project to run code via project-local linter tooling before the user grants project trust, bypassing the IDE's Trust Projects safeguard. The flaw (CWE-829) affects developers who open or import a crafted repository; no public exploit or active exploitation has been identified, and no EPSS/KEV signal is present in the provided data. Fixed in WebStorm 2026.2.

RemediationAI

Vendor-released patch: upgrade WebStorm to 2026.2 or later, which enforces the trust gate before project-local linter tooling is executed; see https://www.jetbrains.com/privacy-security/issues-fixed/. Until upgraded, do not open or import untrusted or unfamiliar repositories in WebStorm, and treat cloning-then-opening a third-party project as a privileged action. As compensating controls, disable automatic linter/ESLint integration (Settings → Languages & Frameworks → JavaScript → Code Quality Tools) so project-local tooling is not auto-run - trade-off: developers lose inline lint feedback until re-enabled - and open suspicious projects only inside a disposable VM or container so any pre-trust code execution is contained. Avoid relying on the Trust Projects prompt alone, since that is the control this vulnerability bypasses.

Affected VersionsENISA

WebStorm 0 <2026.2

Affected Packages

euvd webstorm fix: 2026.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

WebStorm is JetBrains' commercial IDE for JavaScript/TypeScript development, built on the IntelliJ platform. Modern JetBrains IDEs auto-detect and invoke project-local tooling - here linters such as ESLint/TSLint resolved from a project's node_modules and driven by project-checked-in configuration. The Trust Projects security model is designed to defer execution of such automation until the user explicitly trusts a project. This vulnerability maps to CWE-829 (Inclusion of Functionality from an Untrusted Control Sphere): the IDE resolves and executes attacker-controlled linter binaries/config from the untrusted project directory before the trust gate is enforced, so functionality from an untrusted control sphere runs with the developer's privileges.

Know when Webstorm gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (jetbrains) PRIMARY 8.4 HIGH
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local delivery via a malicious project the developer must open (AV:L, UI:R); no auth needed (PR:N); pre-trust code execution yields full local C/I/A impact.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (jetbrains).

CVSS VectorVendor: jetbrains

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Jul 23, 2026 - 14:04 EUVD
CVE Published
Jul 23, 2026 - 12:18 cve.org
HIGH 8.4

DescriptionCVE.org

In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via project-local linter tooling

Executive ViewAI

Why It Matters

JetBrains WebStorm versions prior to 2026.2 contain a code execution vulnerability that bypasses the IDE's project trust safeguards, allowing malicious repositories to execute code without user authorization. Development teams face immediate risk of unauthorized system access and credential theft when opening untrusted external projects. Urgent update to version 2026.2 is required across all development environments.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 96% exploitable
Prevalence
Medium
popular commercial JS/TS IDE, developer-workstation footprint only
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy