6 matches found
CVE-2021-45977
CVE-2021-45977 affects JetBrains IDEs used as Remote Development backends where the affected products bound to the 0.0.0.0 address. The vulnerability description from connected sources notes exposure of the backend service due to binding to an all interfaces address. Fixed versions are provided: ...
CVE-2021-25764
PhpStorm (JetBrains) before 2020.3 is affected: the issue lets source code be written into debug logs (“Source code could be added to debug logs”). The vulnerability affects PhpStorm’s logging path and can lead to information disclosure via logs. The issue is tracked as CVE-2021-25764. Remediatio...
CVE-2024-37051
CVE-2024-37051 describes insufficient protection of GitHub access tokens in multiple JetBrains IDEs, allowing potential exposure of tokens to third-party sites. Affected products/versions include IntelliJ IDEA, Aqua, CLion, DataGrip, DataSpell, GoLand, MPS, PhpStorm, PyCharm, Rider, RubyMine, Rus...
CVE-2022-48435
CVE-2022-48435 affects JetBrains PhpStorm prior to 2023.1. The vulnerability allows source code to be logged in the local idea.log file due to how PhpStorm handles logging. Reported across multiple sources (NVD/Red Hat/CNNVD and related notices). Impact is framed as information disclosure within ...
CVE-2026-64808
Affected software: JetBrains PhpStorm. Vulnerability: via project tooling, PhpStorm before 2026.2 allows arbitrary code execution prior to granting project trust. Root cause is related to the project tooling workflow. Impact: high (as per CVSS 3.1: AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Exploitati...
CVE-2026-64809
JetBrains PhpStorm is affected by CVE-2026-64809: arbitrary code execution possible before granting project trust via the configured interpreter, in PhpStorm before 2026.2. Root cause details are not provided; impact is high with local access and no user interaction required. Exploitation status ...