PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-75060 JetBrains CVE debrief

CVE-2026-75060 debrief based on the supplied source corpus. The vulnerability allows code execution via unauthenticated Jupyter MCP tools in JetBrains PyCharm before 2026.2.1. PyCharm users and administrators should assess exposure and take remediation steps. The CVE record and NVD entry provide details on the vulnerability, but additional verification is necessary to confirm affected scope and severity. Affected product deployments should be identified, and owners assigned for follow-up. Official advisories and CVE records should be reviewed to validate affected scope, severity, and vendor guidance.

Vendor
JetBrains
Product
PyCharm
CVSS
HIGH 8.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-17
Original CVE updated
2026-09-10
Advisory published
2026-08-17
Advisory updated
2026-09-10

Who should care

PyCharm users and administrators should assess exposure and take remediation steps. Affected operator, platform, vulnerability-management, and security-team impact should be considered. Defenders should prioritize verifying exposure and remediation for PyCharm users. Additional verification is necessary to confirm affected scope and severity.

Why it matters

CVE-2026-75060 allows code execution via unauthenticated Jupyter MCP tools in JetBrains PyCharm before 2026.2.1. PyCharm users and administrators should assess exposure, verify remediation, and monitor for suspicious activity.

  • Potential code execution requires verification
  • Unauthenticated access to Jupyter MCP tools may be vulnerable
  • Remediation priority for PyCharm users

Technical summary

JetBrains PyCharm before 2026.2.1 allows code execution via unauthenticated Jupyter MCP tools. The vulnerability has a CVSS score of 8.4 and is classified as HIGH severity. PyCharm users and administrators should assess exposure and take remediation steps. The CVE record and NVD entry provide details on the vulnerability, but additional verification is necessary to confirm affected scope and severity.

Defensive priority

Defenders should prioritize verifying exposure and remediation for PyCharm users.

Recommended defensive actions

  • Verify PyCharm version and apply updates
  • Review Jupyter MCP tool usage and restrict access
  • Monitor for suspicious activity

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. Evidence is limited to public sources, and defenders should verify exposure and remediation for PyCharm users. Additional verification is necessary to confirm affected scope and severity. The vulnerability allows code execution via unauthenticated Jupyter MCP tools in JetBrains PyCharm before 2026.2.1.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-75060 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-75060

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-75060 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-75060

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.