# CVE-2026-64808: Code injection in PhpStorm

> Attackers can execute arbitrary code in JetBrains PhpStorm before project trust is granted via malicious project tooling.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-m97h-r67f-cx3h

## What is CVE-2026-64808?

CVE-2026-64808 is a high-severity code injection vulnerability in JetBrains PhpStorm, published on 23 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In JetBrains PhpStorm before 2026.2 arbitrary code execution was possible before granting project trust via project tooling

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

## Which versions are affected by CVE-2026-64808?

It affects 1 product.


Products: Jetbrains Phpstorm.

## How do I fix CVE-2026-64808?

No fix has been published for CVE-2026-64808 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-64808 being exploited?

There is no known exploitation of CVE-2026-64808 in the wild and no public exploit code.

## Other vulnerabilities in JetBrains PhpStorm

- [CVE-2026-64809](https://insights.sbomify.com/CVE-2026-64809/): Code injection in PhpStorm (high 8.4)
- [CVE-2021-25764](https://insights.sbomify.com/CVE-2021-25764/): Information disclosure in n/a (medium 5.3)
- [CVE-2022-48435](https://insights.sbomify.com/CVE-2022-48435/): Information disclosure in PhpStorm (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64808 and fix it if it is affected.

What it is: CVE-2026-64808 is a high-severity code injection vulnerability in JetBrains PhpStorm, published on 23 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64808 in the wild and no public exploit code.

Affected product: JetBrains PhpStorm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64808/ (Markdown: https://insights.sbomify.com/CVE-2026-64808/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64808
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64808
- OSV: https://osv.dev/vulnerability/CVE-2026-64808

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64808/
Summaries are generated and may contain mistakes; the official description above is the record.