Security readout for executives and security teams
Plain-English summary
PhpStorm versions before 2026.2 could run arbitrary code through a configured interpreter before the user approved project trust. A malicious or compromised project could therefore bypass an important safety boundary, potentially exposing developer credentials, source code, and workstation data.
Executive priority
Treat this as a high-priority developer-endpoint update. Accelerate remediation where PhpStorm users can access proprietary code, cloud credentials, signing material, or production systems. Current evidence does not justify declaring an active incident solely from the CVE.
Technical view
CVE-2026-64809 is a CWE-829 trust-boundary failure affecting JetBrains PhpStorm before 2026.2. The configured interpreter could enable pre-trust code execution. It carries CVSS 3.1 score 8.4 with local access, low complexity, no privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impacts.
Likely exposure
Exposure is most likely on developer workstations running PhpStorm earlier than 2026.2, particularly where projects from external, shared, downloaded, or otherwise untrusted sources are opened. The supplied record does not identify specific operating systems, interpreter types, or enterprise configurations.
Exploitation context
The supplied sources do not report active exploitation, and the CVE is not identified as CISA KEV. Exploitation requires local access according to the CVSS vector, but the precise project-delivery prerequisite and interpreter behavior are not documented in the supplied evidence.
Researcher notes
The central issue is code execution through the configured interpreter before project trust approval. CVSS indicates local, low-complexity exploitation without privileges or user interaction. The supplied material does not describe affected interpreter implementations, detection indicators, exploit availability, or whether opening a crafted project is required; validate those details against updated JetBrains guidance.
Mitigation direction
- Upgrade affected PhpStorm installations to version 2026.2 or later.
- Prioritize workstations handling sensitive repositories, credentials, signing keys, or production access.
- Until upgraded, avoid opening projects from untrusted or unverifiable sources.
- Check JetBrains guidance for any additional configuration-specific mitigations.
Validation and detection
- Inventory PhpStorm versions across developer workstations and build environments.
- Confirm every affected installation reports version 2026.2 or later.
- Review configured interpreters on systems that previously opened untrusted projects.
- Investigate unexpected processes or credential access associated with affected PhpStorm sessions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-829: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-64809 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9JetBrainsVulnerability scoring details
Base CVSS 3.1 score
8.4HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.jetbrains.com/privacy-security/issues-fixed/CVE reference, JetBrains
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.