Plugin execution via automatic LSP server start
Published Aug 20, 2025 · Updated Feb 26, 2026
Untrusted functionality inclusion in IntelliJ IDEA before 2025.2 allows local users to trigger plugin startup through automatic LSP startup. The IDE's automatic LSP-server path starts a plugin without an expected plugin-start action. Exploitation requires low-privilege local access and high-complexity conditions; JetBrains has not disclosed how the plugin is selected.
Summary
What happened
Untrusted functionality inclusion in IntelliJ IDEA before 2025.2 allows local users to trigger plugin startup through automatic LSP startup. The IDE's automatic LSP-server path starts a plugin without an expected plugin-start action. Exploitation requires low-privilege local access and high-complexity conditions; JetBrains has not disclosed how the plugin is selected.
The record
- CVE
- CVE-2025-57729
- Published
- Aug 20, 2025
- Updated
- Feb 26, 2026
- Vendor
- JetBrains
- Product
- IntelliJ IDEA
- Classifications
- CWE-829
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 20, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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 <2025.2
What conditions does exploitation require?
What is affected?
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