Code execution via workspace ID path traversal
Published Jul 10, 2026 · Updated Jul 10, 2026
Path traversal in JetBrains IntelliJ IDEA before 2026.1.4 and before 2026.2 allows remote attackers to execute code through a crafted project. JetBrains identifies project workspace ID handling as the locus but has not published which operation fails to contain the attacker-controlled path. Exploitation requires user interaction with the crafted project and runs code in the security context of the affected IDE process.
Summary
What happened
Path traversal in JetBrains IntelliJ IDEA before 2026.1.4 and before 2026.2 allows remote attackers to execute code through a crafted project. JetBrains identifies project workspace ID handling as the locus but has not published which operation fails to contain the attacker-controlled path. Exploitation requires user interaction with the crafted project and runs code in the security context of the affected IDE process.
The record
- CVE
- CVE-2026-59792
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- JetBrains
- Product
- IntelliJ IDEA
- Classifications
- CWE-23, CAPEC-76, CAPEC-139, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 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.1.4, 2026.2
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