Low severity · published Apr 28, 2022
CVE-2022-29820
In JetBrains PyCharm before 2022.1 exposure of the debugger port to the internal network was possible
3.5
CVSS
0.4%
EPSS
No
On KEV
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Attack vector
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
Low
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.4% · higher than 33% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
PY
Pycharm · Jetbrains
before 2022.1 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2022-29820
CVE.org
https://www.cve.org/CVERecord?id=CVE-2022-29820
Vendor Advisory
https://www.jetbrains.com/privacy-security/issues-fixed/
More from Pycharm
9.8
CVE-2021-45977
JetBrains 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…
8.6
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
8.4
CVE-2026-75060
In JetBrains PyCharm before 2026.2.1 code execution was possible via unauthenticated Jupyter MCP tools
7.8
CVE-2021-30005
In JetBrains PyCharm before 2020.3.4, local code execution was possible because of insufficient checks when getting the project from VCS
7.7
CVE-2022-29821
In JetBrains Rider before 2022.1 local code execution via links in ReSharper Quick Documentation was possible