JetBrains PyCharm

• CVE-2026-118697 Critical 9.0 In JetBrains Toolbox App before 3.9.1 and 3.8.2; IntelliJ IDEA, PyCharm, PhpStorm, RubyMine, WebStorm, GoLand and Rider before 2026.3 and 2026.2.4; CLion before 2026.3 and 2026.2.4.1; DataGrip before 0.3%
• CVE-2026-118696 High 8.0 In JetBrains IntelliJ IDEA, PyCharm, PhpStorm, RubyMine and WebStorm before 2026.3, 2026.2.4, 2026.1.5.1, and 2025.3.6.2; GoLand before 2026.3, 2026.2.4, 2026.1.5.1, and 2025.3.5.2; Rider before 2026. 0.3%
• CVE-2026-75060 High 8.4 In JetBrains PyCharm before 2026.2.1 code execution was possible via unauthenticated Jupyter MCP tools 0.2%
• CVE-2026-75059 Medium 4.4 In JetBrains PyCharm before 2026.2.1 code execution via Quick Documentation was possible 0.2%
• CVE-2026-65908 High 8.6 In JetBrains PyCharm before 2026.1.4, 2026.2 arbitrary code execution via malicious Python executable was possible on untrusted project open 0.2%
• CVE-2026-49384 Medium 6.1 In JetBrains PyCharm before 2025.3.4 stored XSS in Jupyter notebook Markdown cells was possible 0.2%
• CVE-2026-25847 High 8.2 In JetBrains PyCharm before 2025.3.2 a DOM-based XSS on Jupyter viewer page was possible 0.2%
• CVE-2024-37051 Critical 9.3 GitHub access token could be exposed to third-party sites in JetBrains IDEs after version 2023.1 and less than: IntelliJ IDEA 2023.1.7, 2023.2.7, 2023.3.7, 2024.1.3, 2024.2 EAP3; Aqua 2024.1.2; CLion 4.9%
• CVE-2022-29820 Low 3.0 In JetBrains PyCharm before 2022.1 exposure of the debugger port to the internal network was possible 0.4%