EUVD-2026-48231
GHSA-cp73-r8rc-6v5m
Severity by source
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Local because the malicious project must be opened on the host (AV:L); PR:N as no prior privileges are needed, but UI:R since the victim must open the attacker's project, with full C/I/A impact as user.
Primary rating from Vendor (jetbrains).
CVSS VectorVendor: jetbrains
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
3DescriptionCVE.org
In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via the configured Node.js interpreter
Articles & Coverage 2
AnalysisAI
Arbitrary code execution in JetBrains WebStorm before 2026.2 allows a malicious project to run code through the configured Node.js interpreter before the developer grants the project the required trust. Any developer who opens (or clones and opens) an attacker-supplied project is affected, since the IDE's trust prompt - designed to gate execution - is bypassed. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires the victim to open an attacker-controlled project (e.g., a cloned or delivered repository) in WebStorm before version 2026.2, and that project must specify a malicious or attacker-influenced Node.js interpreter path in its configuration; code then runs before the developer clicks 'Trust Project.' Limiting factors: the attacker cannot trigger this remotely over the network (AV:L) - they depend on social engineering or supply-chain delivery to get the project onto the workstation and opened; the impact is bounded to the developer's own user privileges; and environments that only ever open internally-authored, trusted projects are not realistically exposed. Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yields 8.4 (High) with full C/I/A impact, no privileges, and low complexity, but the AV:L attack vector correctly signals this is not a remotely-triggerable network flaw - the attacker must get their project onto the victim's machine and have it opened in WebStorm. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker publishes a seemingly useful open-source repository (or sends a targeted project) whose IDE metadata configures the Node.js interpreter to point at a malicious script. When a developer clones and opens it in WebStorm before 2026.2, the interpreter is invoked prior to the trust prompt, executing the attacker's code on the developer's machine with that user's privileges. … |
| Remediation | Vendor-released patch: WebStorm 2026.2 - upgrade to 2026.2 or later, which is the primary and complete fix (see https://www.jetbrains.com/privacy-security/issues-fixed/). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Inventory all WebStorm installations organization-wide and identify instances running versions before 2026.2; alert affected development teams of the vulnerability and implement temporary restrictions on opening external or untrusted projects. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
Directory traversal vulnerability in lib/app/index.js in Geddy before 13.0.8 for Node.js allows remote attackers to read
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actio
Eval injection vulnerability in index.js in the syntax-error package before 1.1.1 for Node.js 0.10.x, as used in IBM Rat
The HTTP server in Node.js 0.10.x before 0.10.21 and 0.8.x before 0.8.26 allows remote attackers to cause a denial of se
Share
External POC / Exploit Code
Leaving vuln.today