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
|
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 PhpStorm before 2026.2 allows a malicious project to run code through project tooling before the user grants project trust, bypassing the IDE's trust-boundary safeguard. Reported by JetBrains itself (cve@jetbrains.com) and tagged RCE, it lets an attacker who tricks a developer into opening a crafted repository execute code in the developer's context. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the local high-impact (C:H/I:H/A:H) nature makes it relevant for developer-workstation threat models.
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.
Know when Phpstorm 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
Primary rating from Vendor (jetbrains) · only source for this CVE.
CVSS VectorVendor: jetbrains
Lifecycle Timeline
2DescriptionCVE.org
In JetBrains PhpStorm before 2026.2 arbitrary code execution was possible before granting project trust via project tooling
Executive ViewAI
PhpStorm versions before 2026.2 contain a critical flaw in their project trust model that allows arbitrary code execution when developers open untrusted projects, putting development teams at direct risk of intellectual property theft and compromised software builds. Successful exploitation could enable threat actors to inject malicious code into shipped products or internal infrastructure. Every development team using affected PhpStorm versions requires urgent mitigation.
Within 24 hours, inventory all PhpStorm installations earlier than version 2026.2 across development teams and communicate this vulnerability advisory; simultaneously disable auto-execution features for project-level tooling and scripts in PhpStorm settings. Within 7 days, enforce policy requiring manual security review and explicit approval before developers open external repositories, configure PhpStorm to require explicit user trust approval for all projects, and deploy logging to detect suspicious child process execution from PhpStorm. Within 30 days, upgrade all affected PhpStorm installations to version 2026.2 or later once released by JetBrains, and conduct developer security training on identifying and reporting suspicious project structures.
Disable auto-execution of project tools and scripts in IDE settings; require explicit manual approval before opening untrusted repositories; implement enhanced logging and monitoring for process execution spawned by PhpStorm; enforce mandatory security code review before external projects are opened; and provide developer training on suspicious project artifacts.
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.
Arbitrary code execution in JetBrains PhpStorm before 2026.2 allows a malicious project to run attacker-controlled code
The embedded browser in JetBrains desktop IDEs - IntelliJ IDEA, PyCharm, PhpStorm, RubyMine, WebStorm, GoLand, Rider, CL
GitHub access token could be exposed to third-party sites in JetBrains IDEs after version 2023.1 and less than: IntelliJ
In JetBrains PhpStorm before 2020.3, source code could be added to debug logs. Rated medium severity (CVSS 5.3), this vu
EUVD-2026-48233
GHSA-m97h-r67f-cx3h
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB