| CVE-2025-68269 | MEDIO5.4 | In JetBrains IntelliJ IDEA before 2025.3 missing confirmation allowed opening of untrusted remote projects over SSH | 16/12/2025 |
| CVE-2025-57730 | MEDIO4.6 | In JetBrains IntelliJ IDEA before 2025.2 hTML injection was possible via Remote Development feature | 20/08/2025 |
| CVE-2025-57729 | ALTO7.3 | In JetBrains IntelliJ IDEA before 2025.2 unexpected plugin startup was possible due to automatic LSP server start | 20/08/2025 |
| CVE-2025-57728 | MEDIO6.5 | In JetBrains IntelliJ IDEA before 2025.2 improper access control allowed Code With Me guest to discover hidden files | 20/08/2025 |
| CVE-2025-57727 | ALTO7.5 | In JetBrains IntelliJ IDEA before 2025.2 credentials disclosure was possible via remote reference | 20/08/2025 |
| CVE-2025-32054 | BAJO3.3 | In JetBrains IntelliJ IDEA before 2024.3, 2024.2.4 source code could be logged in the idea.log file | 03/04/2025 |
| CVE-2024-46970 | MEDIO6.1 | In JetBrains IntelliJ IDEA before 2024.1 hTML injection via the project name was possible | 16/09/2024 |
| CVE-2024-37051 | ALTO7.5 | 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 2023.1.7, 2023.2.4, 2023.3.5, 2024.1.3, 2024.2 EAP2; DataGrip 2023.1.3, 2023.2.4, 2023.3.5, 2024.1.4; DataSpell 2023.1.6 | 10/06/2024 |
| CVE-2024-24941 | MEDIO5.3 | In JetBrains IntelliJ IDEA before 2023.3.3 a plugin for JetBrains Space was able to send an authentication token to an inappropriate URL | 06/02/2024 |
| CVE-2024-24940 | MEDIO4.3 | In JetBrains IntelliJ IDEA before 2023.3.3 path traversal was possible when unpacking archives | 06/02/2024 |
| CVE-2023-51655 | CRÍTICO9.8 | In JetBrains IntelliJ IDEA before 2023.3.2 code execution was possible in Untrusted Project mode via a malicious plugin repository specified in the project configuration | 21/12/2023 |
| CVE-2023-39261 | ALTO7.8 | In JetBrains IntelliJ IDEA before 2023.2 plugin for Space was requesting excessive permissions | 26/07/2023 |
| CVE-2023-38069 | BAJO3.3 | In JetBrains IntelliJ IDEA before 2023.1.4 license dialog could be suppressed in certain cases | 12/07/2023 |
| CVE-2022-48433 | ALTO7.5 | In JetBrains IntelliJ IDEA before 2023.1 the NTLM hash could leak through an API method used in the IntelliJ IDEA built-in web server. | 29/03/2023 |
| CVE-2022-48432 | ALTO8.8 | In JetBrains IntelliJ IDEA before 2023.1 the bundled version of Chromium wasn't sandboxed. | 29/03/2023 |
| CVE-2022-48431 | ALTO7.8 | In JetBrains IntelliJ IDEA before 2023.1 in some cases, Gradle and Maven projects could be imported without the “Trust Project” confirmation. | 29/03/2023 |
| CVE-2022-48430 | ALTO7.5 | In JetBrains IntelliJ IDEA before 2023.1 file content could be disclosed via an external stylesheet path in Markdown preview. | 29/03/2023 |
| CVE-2022-47896 | ALTO7.8 | In JetBrains IntelliJ IDEA before 2022.3.1 code Templates were vulnerable to SSTI attacks. | 22/12/2022 |
| CVE-2022-47895 | ALTO7.5 | In JetBrains IntelliJ IDEA before 2022.3.1 the "Validate JSP File" action used the HTTP protocol to download required JAR files. | 22/12/2022 |
| CVE-2022-46828 | ALTO7.8 | In JetBrains IntelliJ IDEA before 2022.3 a DYLIB injection on macOS was possible. | 08/12/2022 |