CVE-2026-123308 · Other
NO FIX YET · SEE WHAT TO DO
Before IntelliJ IDEA 2026.3, importing a document inside an untrusted project could execute code. An attacker who gets a developer to open a crafted project could 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 2026.3 are exposed through the document import path. Teams that only open their own trusted repositories have lower exposure. The sources do not give more detail on the exact import trigger.
Not affected if trusted-projects-only, version-2026.3-or-later
Who cares developer-tools, intellij-idea, jetbrains
2026.3 is in the stated range.2026.3 or later (per the NVD description, 'before 2026.3' is affected).In JetBrains IntelliJ IDEA before 2026.3 code execution via the document import was possible in untrusted projects
This page as .md · .json · CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
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.