CVE-2019-14958
CVE-2019-14958 is a high-severity vulnerability in Jetbrains Pycharm with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-770.
Key facts
- Severity: High (CVSS 3.x base score 7.5)
- CVSS v2: 5.0
- EPSS exploit prediction: 2% (81st percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-770
- Affected product: Jetbrains Pycharm
- Published:
- Last modified:
Description
JetBrains 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 message because of Uncontrolled Memory Allocation.
Frequently asked questions
- What is CVE-2019-14958?
- JetBrains 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 message because of Uncontrolled Memory Allocation.
- How severe is CVE-2019-14958?
- CVE-2019-14958 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
- Is CVE-2019-14958 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2019-14958?
- CVE-2019-14958 affects Jetbrains Pycharm. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2019-14958?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2019-14958 published?
- CVE-2019-14958 was published on 2019-10-02 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:jetbrains:pycharm:*:*:*:*:*:*:*:*
More vulnerabilities in Jetbrains Pycharm
- CVE-2021-45977 — Critical (CVSS 9.8): JetBrains IntelliJ IDEA 2021.3.1 Preview, IntelliJ IDEA 2021.3.1 RC, PyCharm Professional 2021.3.1 RC, GoLand 2021.3.1,…
- CVE-2024-37051 — Critical (CVSS 9.3): GitHub access token could be exposed to third-party sites in JetBrains IDEs after version 2023.1 and less than:…
- CVE-2026-65908 — High (CVSS 8.6): In JetBrains PyCharm before 2026.1.4, 2026.2 arbitrary code execution via malicious Python executable was possible on…
- CVE-2026-75060 — High (CVSS 8.4): In JetBrains PyCharm before 2026.2.1 code execution was possible via unauthenticated Jupyter MCP tools
- CVE-2026-25847 — High (CVSS 8.2): In JetBrains PyCharm before 2025.3.2 a DOM-based XSS on Jupyter viewer page was possible
- CVE-2021-30005 — High (CVSS 7.8): In JetBrains PyCharm before 2020.3.4, local code execution was possible because of insufficient checks when getting the…
All CVEs affecting Jetbrains Pycharm →
Other CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities
- CVE-2026-63299 — Critical (CVSS 9.9): An authorization bypass vulnerability in LXD allows an authenticated user to bypass project-level disk and volume…
- CVE-2026-112779 — Critical (CVSS 9.8): Grav API plugin (grav-plugin-api) 1.0.40 before 1.0.42 caches a full translation dictionary for every well-formed…
- CVE-2026-82439 — Critical (CVSS 9.8): Description The DRPC server kept a map from function name to request queue and created an entry the first time…
- CVE-2026-47891 — Critical (CVSS 9.8): A Spring WebFlux application that relies on the Aalto XML processor to parse XML input does not correctly enforce the…
- CVE-2026-74878 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.0 use an in-memory rate limiter for TOTP brute-force protection that is not shared…
- CVE-2026-31283 — Critical (CVSS 9.8): In Totara LMS v19.1.5 and before, the forgot password API does not implement rate limiting for the target email…
Browse all CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities →