Local privilege escalation via uncontrolled DLL search
Published Dec 10, 2025 · Updated Dec 10, 2025
DLL hijacking in Lenovo One Client 2.8.200.5081 and earlier allows local users to execute code with elevated privileges. Lenovo identifies an uncontrolled DLL search path but does not disclose the executable, DLL name, or directory that accepts attacker-controlled code. A local authenticated account is required; successful exploitation runs supplied code with the affected component's privileges.
Summary
What happened
DLL hijacking in Lenovo One Client 2.8.200.5081 and earlier allows local users to execute code with elevated privileges. Lenovo identifies an uncontrolled DLL search path but does not disclose the executable, DLL name, or directory that accepts attacker-controlled code. A local authenticated account is required; successful exploitation runs supplied code with the affected component's privileges.
The record
- CVE
- CVE-2025-13152
- Published
- Dec 10, 2025
- Updated
- Dec 10, 2025
- Vendor
- Lenovo
- Product
- Lenovo One Client
- Classifications
- CWE-427, T1574.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 10, 2025CVE publishedPublication date reported by the CVE source.
- Dec 10, 2025Record 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 <=2.8.200.5081
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