Skip to content
Weekly Signal
Live intelligence Updated 21 Aug 2026 · 22:12 UTC

JetBrains · Pycharm

CVE-2026-65908

In JetBrains PyCharm before 2026.1.4, 2026.2 arbitrary code execution via malicious Python executable was possible on untrusted project open

Recommended action

Handle this through the normal risk-based patching cycle while monitoring for change. Vendor advisory from www.jetbrains.com

View response plan
CVSS8.6
EPSS0.1%
KEVNo
ExploitationNone
RemediationNot yet verified

Assessment

Why it matters

EPSS is 0.1%; technical severity is CVSS 8.6.

In JetBrains PyCharm before 2026.1.4, 2026.2 arbitrary code execution via malicious Python executable was possible on untrusted project open

Who should care

  • Teams operating Pycharm
  • Vulnerability and exposure management teams
  • Security operations teams monitoring exploitation activity

Response plan

What I would do

  1. Confirm whether Pycharm is present in the environment.
  2. Identify affected versions and establish whether vulnerable services are exposed or reachable.
  3. Vendor advisory from www.jetbrains.com
  4. Review relevant security telemetry for evidence of attempted or successful exploitation.
  5. Document the remediation decision and track it to verified completion.

Treatment intelligence

Remediation intelligence

Not yet verified

Vendor sources are listed before government and third-party guidance. Confirm product applicability and change prerequisites before deployment.

Verification noteAutomated link verification has not completed for this guidance yet.

Technical details

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CWE
CWE-829
Affected versions
JetBrains Pycharm (End Excluding 2026.1.4)
Fixed versions
JetBrains Pycharm (Fixed from 2026.1.4)
Published
23 July 2026
Attack vector
Local
Privileges required
None
User interaction
Required

Signal timeline

  1. CVE published
  2. Latest EPSS score: 0.1%
  3. Signal calculated at 12

External references

Live public intelligence This assessment combines public-source evidence. Validate the affected product, version and exposure against your own environment before making a risk decision.