Code execution via malicious Python executable
Published Jul 23, 2026 · Updated Jul 23, 2026
CWE-829 in JetBrains PyCharm before 2026.1.4 allows attackers to execute code when an untrusted project is opened. JetBrains identifies the locus only as handling of a malicious Python executable and has not disclosed the faulty validation or launch logic. Opening an attacker-controlled project is required, after which the executable runs with the IDE user's privileges.
Summary
What happened
CWE-829 in JetBrains PyCharm before 2026.1.4 allows attackers to execute code when an untrusted project is opened. JetBrains identifies the locus only as handling of a malicious Python executable and has not disclosed the faulty validation or launch logic. Opening an attacker-controlled project is required, after which the executable runs with the IDE user's privileges.
The record
- CVE
- CVE-2026-65908
- Published
- Jul 23, 2026
- Updated
- Jul 23, 2026
- Vendor
- JetBrains
- Product
- PyCharm
- Classifications
- CWE-829, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 23, 2026CVE publishedPublication date reported by the CVE source.
- Jul 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.1.4, 2026.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo