Code execution via Markdown export command injection
Published Aug 17, 2026 · Updated Aug 18, 2026
Command injection in JetBrains IntelliJ IDEA before 2026.2.1 allows attackers to execute code via the Markdown export tool. JetBrains classifies the flaw as CWE-78 in that export path, but the vendor has not published the affected function or the exact unsafe command-building step on untrusted Markdown input. Exploitation is local and requires user interaction to export attacker-controlled Markdown, after which code runs with the privileges of the IntelliJ IDEA process.
Summary
What happened
Command injection in JetBrains IntelliJ IDEA before 2026.2.1 allows attackers to execute code via the Markdown export tool. JetBrains classifies the flaw as CWE-78 in that export path, but the vendor has not published the affected function or the exact unsafe command-building step on untrusted Markdown input. Exploitation is local and requires user interaction to export attacker-controlled Markdown, after which code runs with the privileges of the IntelliJ IDEA process.
The record
- CVE
- CVE-2026-75056
- Published
- Aug 17, 2026
- Updated
- Aug 18, 2026
- Vendor
- JetBrains
- Product
- IntelliJ IDEA
- Classifications
- CWE-78, T1204.002, T1059
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 17, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo