VulnerabilityPublished 25 Sep 2025Updated 30 Sep 2025

CVE-2025-10941: Topaz SERVCore Teller · Permission Issues

Affects Topaz SERVCore TellerSource CVE Database V5

Not known to be exploited · CVSS 8.5 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score

8.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Topaz SERVCore Teller	Affected =2.14.0-RC2 =2.14.1	Fixed in–

AI-suggested

European organizations should prioritize upgrading to the latest version of the SERVCore Teller installer that no longer uses "nssm" to eliminate this vulnerability. In addition, organizations should enforce strict local access controls and monitoring to detect and prevent unauthorized local access attempts. Implementing endpoint security solutions that can detect privilege escalation attempts and anomalous installer manipulations is recommended. Regular audits of user permissions and system logs can help identify suspicious activities early. Network segmentation to isolate teller systems and restrict access to only authorized personnel will reduce the attack surface. Since the vulnerability requires local access, strengthening physical security and endpoint hardening measures is critical. Finally, organizations should maintain an incident response plan tailored to privilege escalation incidents to respond swiftly if exploitation is suspected.

Description

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".

Impact

For European organizations using Topaz SERVCore Teller, particularly in financial or banking sectors where this software is likely deployed, this vulnerability poses a significant risk. An attacker with local access could exploit the permission issues to escalate privileges, potentially gaining unauthorized access to sensitive financial data or critical system functions. This could lead to data breaches, manipulation of transaction records, or disruption of teller operations. The impact on confidentiality is high due to possible unauthorized data access; integrity is at risk because of potential unauthorized modifications; and availability could be affected if the attacker disrupts service components. Given the local attack vector, insider threats or compromised endpoints within the organization's network are the primary concern. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially in environments with less stringent internal access controls.

Summary

CVE-2025-10941 is a high-severity vulnerability identified in Topaz SERVCore Teller versions 2.14.0-RC2 and 2.14.1, specifically related to the Installer component within the SERVCoreTeller_2.0.40D.msi file. The vulnerability arises from permission issues caused by the use of "nssm" (Non-Sucking Service Manager), a service manager utility that was part of the installer. This flaw allows a local attacker with limited privileges (low-level privileges) to manipulate the installer in a way that escalates permissions, potentially granting higher access rights than intended. The attack requires local access to the affected system, meaning remote exploitation is not feasible without prior access. The vendor has addressed this vulnerability by removing the dependency on "nssm" in the latest installer versions, effectively mitigating the issue. The CVSS 4.0 base score of 8.5 reflects the high impact on confidentiality, integrity, and availability, with low attack complexity and no user interaction required. However, the vulnerability does not require elevated privileges to initiate but does require local access, limiting the attack vector to insiders or users with some system access. No known exploits are currently reported in the wild, but the potential for privilege escalation makes this a significant risk in environments where SERVCore Teller is deployed.

References

Community reviews

Loading reviews…