LocalSystem escalation via unquoted service path
Published May 16, 2026 · Updated May 16, 2026
An unquoted service path in KiteService in Kite 4.2.0.1 U1 and earlier allows local users to execute code as LocalSystem. KiteService registers C:\Program Files\Kite\KiteService.exe without surrounding quotes, so Windows can resolve an attacker-controlled executable first. Exploitation requires write access to an earlier path component and occurs when the LocalSystem service starts.
Summary
What happened
An unquoted service path in KiteService in Kite 4.2.0.1 U1 and earlier allows local users to execute code as LocalSystem. KiteService registers C:\Program Files\Kite\KiteService.exe without surrounding quotes, so Windows can resolve an attacker-controlled executable first. Exploitation requires write access to an earlier path component and occurs when the LocalSystem service starts.
The record
- CVE
- CVE-2020-37247
- Published
- May 16, 2026
- Updated
- May 16, 2026
- Vendor
- Kite
- Product
- Kite
- Classifications
- CWE-428, T1574.009
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 16, 2026CVE publishedPublication date reported by the CVE source.
- May 16, 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=4.2.0.1 U1
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
- Kite 1.2021.610.0 - Unquoted Service Pathproof of concept · demonstrated
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