CVE-2026-75060: In JetBrains PyCharm before 2026.2.1 code execution was possible via unauthenticated Jupyter MCP tools

Routine

HIGH 8.4UPGRADE

CVE-2026-75060 is a high-severity flaw (CVSS 8.4) affecting pycharm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In JetBrains PyCharm before 2026.2.1 code execution was possible via unauthenticated Jupyter MCP tools

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.4 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 93%)
CISA exploited list	No
Weakness	CWE-306
Published	2026-08-17
Last modified	2026-10-23

Publisher (CNA): JetBrains s.r.o. · Vendor: jetbrains

Am I affected?

Timeline

2026-08-17 16:17 UTCPublished CVE record published
2026-10-23 16:10 UTCUpdated Record last modified

jetbrains pycharm UPGRADE

Affected: < 2026.2.1

Fixed in: 2026.2.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy pycharm || rpm -q pycharm || pycharm --version

2. UPGRADE to 2026.2.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pycharm

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pycharm

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Exact fixes by distribution

Fedora 46 · gum · FIXED · 2.0.2-1.fc46 · FEDORA-2026-da0d6dd894 · source

sudo dnf upgrade --advisory=FEDORA-2026-da0d6dd894

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Related CVEs

CVE-2026-75059 MEDIUM 4.4 UPGRADE In JetBrains PyCharm before 2026.2.1 code execution via Quick Documentation was possible

References

← Back to latest CVEs