CVE-2026-75060
Unauthenticated Jupyter MCP in PyCharm allows remote code execution
Is CVE-2026-75060 being exploited?
Not confirmed. CVE-2026-75060 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-75060?
CVE-2026-75060 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-75060?
Yes. A fix has been recorded for CVE-2026-75060. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-75060 affect?
CVE-2026-75060 affects JetBrains PyCharm < 2026.2.1 (Jupyter MCP). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-75060?
Upgrade to PyCharm 2026.2.1 now; disable Jupyter MCP if you cannot patch immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote code execution via Jupyter MCP in PyCharm, enabling arbitrary code execution with the user's privileges and potential project/data compromise.
Immediate action required
- affected< 2026.2.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.