EUVD-2026-48252
GHSA-2j8g-fr3j-fp7c
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 PyCharm before 2026.1.4 and 2026.2 lets an attacker who supplies a crafted project achieve code execution when a victim opens that untrusted project in the IDE. PyCharm auto-selects or trusts a Python executable bundled or referenced by the project, so merely opening the malicious project runs attacker-controlled code with the user's privileges. No public exploit identified at time of analysis, and it is not listed in CISA KEV, but the reporter is JetBrains itself and a vendor patch is available.
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 Pycharm 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:R/S:C/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 PyCharm before 2026.1.4, 2026.2 arbitrary code execution via malicious Python executable was possible on untrusted project open
Articles & Coverage 1
Executive ViewAI
CVE-2026-65908 in JetBrains PyCharm enables arbitrary code execution when developers open untrusted projects, as the IDE automatically executes bundled Python interpreters without user consent. This vulnerability affects PyCharm versions before 2026.1.4 and 2026.2, exposing development teams to supply-chain attacks through malicious project repositories. Organizations must prioritize immediate patching to prevent compromise of developer workstations and unauthorized access to source code.
Within 24 hours, inventory all PyCharm installations across development and CI/CD environments to identify affected versions. Within 7 days, upgrade all PyCharm instances to version 2026.1.4 or later in the 2026.1 branch, or 2026.2 or later in the 2026.2 branch, per JetBrains guidance. Within 30 days, audit recent projects opened in formerly affected PyCharm versions, review external project sources for unauthorized modifications, and conduct security awareness training emphasizing the risks of opening untrusted projects.
Apply vendor patch. Until patching is complete, restrict project opening to verified internal repositories and educate developers to decline auto-trust prompts for external projects.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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.
In JetBrains PyCharm 2019.2.5 and 2019.3 on Windows, Apple Notarization Service credentials were included. Rated high se
Code execution in JetBrains PyCharm before 2026.2.1 is possible through Jupyter MCP (Model Context Protocol) tools that
In JetBrains PyCharm before 2025.3.2 a DOM-based XSS on Jupyter viewer page was possible [CVSS 8.2 HIGH]
The embedded browser in JetBrains desktop IDEs - IntelliJ IDEA, PyCharm, PhpStorm, RubyMine, WebStorm, GoLand, Rider, CL
In JetBrains PyCharm before 2020.3.4, local code execution was possible because of insufficient checks when getting the
In JetBrains Rider before 2022.1 local code execution via links in ReSharper Quick Documentation was possible. Rated hig
GitHub access token could be exposed to third-party sites in JetBrains IDEs after version 2023.1 and less than: IntelliJ
JetBrains PyCharm before 2019.2 was allocating a buffer of unknown size for one of the connection processes. Rated high
Stored XSS in JetBrains PyCharm's Jupyter notebook Markdown cell renderer allows a remote, unauthenticated attacker to e
Cross-site scripting in JetBrains PyCharm's Quick Documentation rendering feature (before version 2026.2.1) enables code
In JetBrains PyCharm before 2022.1 exposure of the debugger port to the internal network was possible. Rated low severit
Exploit-DB