CVE-2026-123853 · Other
NO FIX YET · SEE WHAT TO DO
Before IntelliJ IDEA 2026.3 and 2026.2.2, a project could control JVM options used by the build process, letting code run even when Safe Mode was active. An attacker who gets a developer to open a malicious project can run code on that developer's machine.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Developers who open untrusted or third-party projects in IntelliJ IDEA before the fixed versions, relying on Safe Mode for protection. Teams that only open their own trusted projects face less risk. unknown for whether build-only or runtime setups are affected beyond this.
Not affected if trusted-projects-only, up-to-date-ide
Who cares developer-workstation, intellij-idea, java, jetbrains
2026.3 or 2026.2.2, the first releases listed as fixed in the source.In JetBrains IntelliJ IDEA before 2026.3, 2026.2.2 code execution was possible in Safe Mode via project-controlled JVM options of the build process
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.