Arbitrary code execution via unvalidated LSP binary
Published Sep 7, 2026 · Updated Sep 8, 2026
OS command injection in Knowns before 0.30.0 allows attackers to execute arbitrary binaries by opening a crafted project repository. ProjectSettings.Validate ignores settings.lsp.languages..binary, and Detector.resolve passes the resulting path to a version check before Server.Start spawns it again. Opening an attacker-controlled repository is required, after which both executions run under the affected user's account.
Summary
What happened
OS command injection in Knowns before 0.30.0 allows attackers to execute arbitrary binaries by opening a crafted project repository. ProjectSettings.Validate ignores settings.lsp.languages..binary, and Detector.resolve passes the resulting path to a version check before Server.Start spawns it again. Opening an attacker-controlled repository is required, after which both executions run under the affected user's account.
The record
- CVE
- CVE-2026-86540
- Published
- Sep 7, 2026
- Updated
- Sep 8, 2026
- Vendor
- Knowns
- Product
- Knowns
- Classifications
- CWE-78, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 7, 2026CVE publishedPublication date reported by the CVE source.
- Sep 8, 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 <0.30.0
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