Skip to main content

Phpstorm CVE-2026-64808

| EUVDEUVD-2026-48233 HIGH
Inclusion of Functionality from Untrusted Control Sphere (CWE-829)
2026-07-23 cve@jetbrains.com GHSA-m97h-r67f-cx3h
8.4
CVSS 3.1 · Vendor: jetbrains
View

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
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 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

PhpStorm 0 <2026.2

Affected Packages

euvd phpstorm 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.

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

Vendor (jetbrains) PRIMARY 8.4 HIGH
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

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 PhpStorm before 2026.2 arbitrary code execution was possible before granting project trust via project tooling

Executive ViewAI

Why It Matters

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.

Recommended Action

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.1%
Top 96% exploitable
Data Quality
5 sources
Confidence: Medium

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