CVE Tools
Track your stack

Pycharm

15 CVEs tracked. None of them is in CISA KEV.

This hub aggregates every CVE we track for Pycharm, a product in the devtools ci space. Use it to gauge the current risk picture and drill into individual advisories.

Pycharm CVEs per month

Dec 2024 to Nov 2026. Point at a month, or focus the strip and use the arrow keys.
Pycharm CVEs per month
MonthCVEs
2024-120
2025-010
2025-020
2025-030
2025-040
2025-050
2025-060
2025-070
2025-080
2025-090
2025-100
2025-110
2025-120
2026-010
2026-021
2026-030
2026-040
2026-051
2026-060
2026-071
2026-082
2026-090
2026-102
2026-111

Severity

How the 15 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.

  • Critical320%
  • High747%
  • Medium427%
  • Low17%

Latest CVEs

The 15 most recently published vulnerabilities affecting Pycharm.

  1. CVE-2026-123854In JetBrains PyCharm before 2026.3 code execution was possible in Safe Mode via a crafted Jupyter notebook widget module5.5
  2. CVE-2026-118697In 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 befo...9.0
  3. CVE-2026-118696In 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 20...8.0
  4. CVE-2026-75059In JetBrains PyCharm before 2026.2.1 code execution via Quick Documentation was possible4.4
  5. CVE-2026-75060In JetBrains PyCharm before 2026.2.1 code execution was possible via unauthenticated Jupyter MCP tools8.4
  6. CVE-2026-65908In JetBrains PyCharm before 2026.1.4, 2026.2 arbitrary code execution via malicious Python executable was possible on untrusted project open8.6
  7. CVE-2026-49384In JetBrains PyCharm before 2025.3.4 stored XSS in Jupyter notebook Markdown cells was possible6.1
  8. CVE-2026-25847In JetBrains PyCharm before 2025.3.2 a DOM-based XSS on Jupyter viewer page was possible8.2
  9. CVE-2024-37051GitHub 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; CLi...9.3
  10. CVE-2022-29821In JetBrains Rider before 2022.1 local code execution via links in ReSharper Quick Documentation was possible6.9
  11. CVE-2022-29820In JetBrains PyCharm before 2022.1 exposure of the debugger port to the internal network was possible3.0
  12. CVE-2021-45977JetBrains IntelliJ IDEA 2021.3.1 Preview, IntelliJ IDEA 2021.3.1 RC, PyCharm Professional 2021.3.1 RC, GoLand 2021.3.1, PhpStorm 2021.3.1 Preview, PhpStorm 2021.3.1 RC, RubyMine 2021.3.1 Preview, R...9.8
  13. CVE-2021-30005In JetBrains PyCharm before 2020.3.4, local code execution was possible because of insufficient checks when getting the project from VCS.7.8
  14. CVE-2020-11694In JetBrains PyCharm 2019.2.5 and 2019.3 on Windows, Apple Notarization Service credentials were included. This is fixed in 2019.2.6 and 2019.3.3.7.5
  15. CVE-2019-14958JetBrains PyCharm before 2019.2 was allocating a buffer of unknown size for one of the connection processes. In a very specific situation, it could lead to a remote invocation of an OOM error messa...7.5

Product grouping is registry-driven, with AI assist and human review. How it works