JetBrains IntelliJ IDEA vulnerabilities

In JetBrains IntelliJ IDEA versions before 2024.3.7.1, 2025.1.7.1, 2025.2.6.2, 2025.3.4.1, and 2026.1.1, it was possible to read arbitrary local files via the built-in web server.

In JetBrains IntelliJ IDEA before version 2026.2, unauthorized input injection is possible during a Remote Development session.

In JetBrains IntelliJ IDEA before version 2026.2.3, remote code execution (RCE) via Structural Search script constraints was possible in untrusted projects.

In JetBrains IntelliJ IDEA before 2026.2.2 missing project-trust check leaked project metadata to JetBrains Marketplace.

In JetBrains IntelliJ IDEA before 2026.2.2 opening an untrusted project could trigger SSRF via Kubernetes spec-source URL fetching.

In JetBrains IntelliJ IDEA before 2026.2.2 terminal command input could be written to idea.log.

In JetBrains IntelliJ IDEA before 2026.2.1 XXE was possible in the Eclipse settings importers.

In JetBrains IntelliJ IDEA before 2026.1.5 git credentials were written in plaintext to the IDE log.

In JetBrains IntelliJ IDEA before 2026.2.1, remote code execution (RCE) was possible via the Markdown export tool.

In JetBrains IntelliJ IDEA before 2026.2.1 hadoop ResourceManager could read local files via XXE.

In JetBrains IntelliJ IDEA before 2026.2.1 SSRF was possible via the OpenAPI preview proxy in untrusted projects.

In JetBrains IntelliJ IDEA before 2026.2.1, a Server-Side Request Forgery (SSRF) was possible via the DevKit debug listener endpoint.

In JetBrains IntelliJ IDEA before 2026.2.1, command execution via crafted Markdown preview content was possible in trusted projects.

Vulnerability in JetBrains IntelliJ IDEA before version 2026.2 allows arbitrary code injection via UI Designer form files.

In JetBrains IntelliJ IDEA before version 2026.2, arbitrary code execution was possible before granting project trust via development container configuration.

In JetBrains IntelliJ IDEA before version 2026.2, HTML injection was possible in IDE notifications, allowing silent user activity tracking.

In JetBrains IntelliJ IDEA before 2026.1, code execution was possible via template injection in the Copyright plugin.

In JetBrains IntelliJ IDEA before 2026.1.1 command execution was possible via the guest user account.

In JetBrains IntelliJ IDEA before 2026.1.1, command injection was possible via filename completion.

In JetBrains IntelliJ IDEA before version 2023.1.4, the license dialog could be suppressed in certain cases.

In JetBrains IntelliJ IDEA before 2022.2 local code execution via a Vagrant executable was possible. This vulnerability allowed execution of malicious code in the user's context.