Loading vulnerability…
CVE-2026-65908 is an arbitrary code execution vulnerability in JetBrains PyCharm affecting versions before 2026.1.4 and 2026.2. The flaw is triggered when PyCharm opens an untrusted project and processes a malicious Python executable associated with that project before trust protections fully prevent execution. The issue is classified as CWE-829, indicating inclusion or execution of functionality from an untrusted control sphere. Successful exploitation can occur during project opening and results in execution of attacker-controlled code in the context of the user running the IDE.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A JetBrains vulnerability listed among the patched issues; the article does not further describe the flaw beyond its CWE and fixed versions.
An arbitrary code execution vulnerability in JetBrains PyCharm that could be triggered when opening an untrusted project containing a malicious Python executable.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.