Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft repo with malicious project-local linter
-
DeliveryLure developer to clone and open in WebStorm
-
ExploitIDE auto-invokes linter before trust granted
-
ExecutionAttacker code executes with developer privileges
-
ImpactCompromise 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
Primary rating from Vendor (jetbrains).
CVSS VectorVendor: jetbrains
Lifecycle Timeline
2DescriptionCVE.org
In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via project-local linter tooling
Executive ViewAI
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.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
In JetBrains WebStorm before 2021.1, code execution without user confirmation was possible for untrusted projects. Rated
Arbitrary code execution in JetBrains WebStorm before 2026.2 allows a malicious project to run code through the configur
Arbitrary code execution in JetBrains WebStorm before 2026.2 lets a malicious project run code on a developer's machine
The embedded browser in JetBrains desktop IDEs - IntelliJ IDEA, PyCharm, PhpStorm, RubyMine, WebStorm, GoLand, Rider, CL
Arbitrary code execution in JetBrains WebStorm before 2026.2 allows a malicious project to run attacker-controlled code
In JetBrains WebStorm before 2024.3 code execution in Untrusted Project mode was possible via type definitions installer
GitHub access token could be exposed to third-party sites in JetBrains IDEs after version 2023.1 and less than: IntelliJ
In JetBrains WebStorm before 2021.1, HTTP requests were used instead of HTTPS. Rated high severity (CVSS 7.5), this vuln
EUVD-2026-48229
GHSA-x88m-wx27-x7m2
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB