SYSTEM code execution via pre-created service directory
Published Sep 25, 2025 · Updated Sep 25, 2025
Local privilege escalation in Topaz SERVCore Teller 2.14.0-RC2 and 2.14.1 allows local users to execute code as SYSTEM. The installer creates the SERVCoreSmartClient service but neither checks nor resets ACLs on C:\ProgramData\SERVCoreTeller\Service, letting a pre-created directory remain user-controlled. A local unprivileged user must create the directory before administrative installation, replace nssm.exe afterward, and wait for a reboot to trigger SYSTEM execution.
Summary
What happened
Local privilege escalation in Topaz SERVCore Teller 2.14.0-RC2 and 2.14.1 allows local users to execute code as SYSTEM. The installer creates the SERVCoreSmartClient service but neither checks nor resets ACLs on C:\ProgramData\SERVCoreTeller\Service, letting a pre-created directory remain user-controlled. A local unprivileged user must create the directory before administrative installation, replace nssm.exe afterward, and wait for a reboot to trigger SYSTEM execution.
The record
- CVE
- CVE-2025-10941
- Published
- Sep 25, 2025
- Updated
- Sep 25, 2025
- Vendor
- Topaz
- Product
- SERVCore Teller
- Classifications
- CWE-275, CWE-266, T1574.010
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 25, 2025CVE publishedPublication date reported by the CVE source.
- Sep 25, 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=2.14.0-RC2
- Affected versionversion=2.14.1
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