dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-10941

HIGH · 7.8 CVSS v3.1 Published 2025-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was determined in Topaz SERVCore Teller 2.14.0-RC2/2.14.1. Affected by this issue is some unknown functionality of the file SERVCoreTeller_2.0.40D.msi of the component Installer. Executing manipulation can lead to permission issues. The attack needs to be launched locally. You should upgrade the affected component. The vendor explains, that "this vulnerability was detected at the beginning of 2025, it was remediated because the latest published version of the installer no longer uses "nssm," which is responsible for this vulnerability".

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The vulnerability exists in the Topaz SERVCore Teller installer (SERVCoreTeller_2.0.40D.msi) which uses the nssm (Non-Sucking Service Manager) tool to install Windows services. The manipulation of the installer leads to permission issues, likely involving improper service configuration allowing privilege escalation or unauthorized service manipulation. The attack requires local access.

MitigationUpgrade to the latest version of Topaz SERVCore Teller where the vendor has removed the nssm dependency, eliminating this permission vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Topaz SERVCore Teller installation
    Check Add/Remove Programs or Program Files for Topaz SERVCore Teller. Look for SERVCoreTeller_2.0.40D.msi in installed programs or search for 'Topaz' or 'SERVCore' in the system.
    Affected if The application is installed and the version is 2.0.40D or earlier
  2. Identify installed version
    Open the Windows installer database (MSI) or check the installed program's version property. In PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*SERVCore*'} | Select-Object DisplayName, DisplayVersion
    Affected if Version displayed is 2.0.40D or any version prior to the vendor fix
  3. Locate nssm.exe in the application directory
    Search the Topaz SERVCore installation folder for nssm.exe (Non-Sucking Service Manager). Common paths: C:\Program Files\Topaz\SERVCore\ or the install directory found in registry.
    Affected if nssm.exe exists in the Topaz installation directory, indicating the vulnerable tool is present
  4. Inspect Windows services installed by the application
    Run 'sc query' or open Services.msc and look for services with 'Topaz', 'SERVCore', or 'Teller' in the name. Check the service binary path using 'sc qc <servicename>' to confirm it references nssm.exe.
    Affected if A Topaz-related Windows service exists and its binary path points to nssm.exe or references the Topaz installer path containing nssm
  5. Check service file permissions
    Use icacls or PowerShell Get-Acl on the nssm.exe binary and any Topaz service executables. Verify if non-admin users have write or modify permissions to these files.
    Affected if Non-privileged users have write, modify, or full control permissions on nssm.exe or service-related executables in the Topaz installation folder

You are affected if Topaz SERVCore Teller version 2.0.40D or earlier is installed AND nssm.exe is present in the application directory, creating a potential privilege escalation vector through service configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the latest version of Topaz SERVCore Teller where the vendor has removed the nssm dependency, eliminating this permission vulnerability.

Recommended fix Moderate confidence

Latest version of SERVCoreTeller (vendor states nssm has been removed)

  1. Contact Topaz to obtain the latest version of SERVCoreTeller installer that no longer uses nssm
  2. Verify the new installer version does not include the nssm.exe utility
  3. Apply the latest installer to update Topaz SERVCore Teller

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10941 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10941 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data