Security readout for executives and security teams
Plain-English summary
PhpStorm versions before 2026.2 could run arbitrary code through project tooling before the user granted project trust. A malicious or compromised project could therefore bypass an important safety boundary, potentially exposing developer credentials, source code, and the workstation.
Executive priority
Treat this as a high-priority developer-workstation update. Accelerate remediation where PhpStorm users access sensitive repositories, production credentials, or third-party projects. There is no supplied evidence of active exploitation, but successful abuse could fully compromise a developer endpoint.
Technical view
CVE-2026-64808 is a local, low-complexity code-execution flaw classified as CWE-829. It requires no privileges or user interaction under the published CVSS vector and can affect confidentiality, integrity, and availability. The disclosed sources do not explain the precise tooling component or execution mechanism.
Likely exposure
Exposure centers on PhpStorm installations older than 2026.2, particularly systems handling externally sourced or otherwise untrusted projects. The supplied affected-version metadata is ambiguous, listing version “0” while the title identifies releases before 2026.2.
Exploitation context
The CVSS vector indicates local access, low complexity, no privileges, and no user interaction. The supplied sources provide no evidence of public exploitation or active attacks, and the CVE is not listed as KEV in the bundle.
Researcher notes
The disclosure establishes pre-trust code execution but provides limited root-cause detail. CVSS is 8.4 with AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The version metadata conflicts with the narrative boundary, so validate affected releases against current JetBrains guidance before final exposure reporting.
Mitigation direction
- Upgrade PhpStorm to version 2026.2 or later.
- Check JetBrains guidance for additional remediation or configuration advice.
- Restrict handling of untrusted projects until affected installations are upgraded.
- Prioritize developer systems containing credentials, signing keys, or sensitive source code.
Validation and detection
- Inventory PhpStorm installations and identify versions earlier than 2026.2.
- Confirm upgraded endpoints report PhpStorm 2026.2 or later.
- Review JetBrains advisories for updated affected-version or mitigation details.
- Investigate unusual process execution associated with PhpStorm on previously affected endpoints.
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-64808 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.