VulnerabilityPublished 15 Mar 2026Updated 16 Mar 2026

CVE-2026-4170: Topsec TopACM · OS Command Injection

Affects Topsec TopACMSource CVE Database V5

Compare

Public exploit available · CVSS 9.3 Critical.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

9.3Critical

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

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

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
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

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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
TopsecTopACM	Affected =3.0	Fixed in–

AI-suggested

In the absence of an official patch from Topsec, organizations should implement immediate compensating controls. These include restricting network access to the affected TopACM management interfaces using firewalls or VPNs to limit exposure to trusted administrators only. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious input patterns targeting the 'template_path' parameter. Conduct thorough monitoring and logging of all requests to the vulnerable endpoint to detect exploitation attempts early. If possible, isolate the affected system in a segmented network zone to reduce lateral movement risk. Organizations should also consider deploying host-based intrusion detection systems (HIDS) to identify unusual command executions. Regular backups and incident response plans should be updated to prepare for potential compromise. Finally, maintain active communication with Topsec for updates and apply any future patches promptly once available.

Description

CVE-2026-4170 is a critical OS command injection vulnerability in Topsec TopACM version 3.0, specifically in the HTTP request handler component at /view/systemConfig/management/nmc_sync.php. The vulnerability arises from improper sanitization of the 'template_path' argument, allowing remote attackers to execute arbitrary OS commands without authentication or user interaction. The exploit is publicly available, increasing the risk of exploitation, although no active attacks have been reported yet. The vendor has not responded to disclosure attempts, and no patches are currently available. This vulnerability can lead to full system compromise, data theft, or disruption of services. Organizations using TopACM 3.0 should prioritize mitigation to prevent potential exploitation. Countries with significant deployments of Topsec products, especially in Asia and parts of Europe, are at higher risk.

Impact

The impact of CVE-2026-4170 is severe for organizations using Topsec TopACM 3.0. Successful exploitation allows remote attackers to execute arbitrary OS commands, leading to full system compromise. This can result in unauthorized access to sensitive data, disruption or destruction of services, installation of persistent malware, and lateral movement within the network. Given that the vulnerability requires no authentication and no user interaction, it significantly lowers the barrier for attackers, including automated bots and opportunistic threat actors. The public availability of exploit code further increases the risk of widespread attacks. Organizations in critical infrastructure sectors, government, and enterprises relying on TopACM for security management or network configuration are particularly at risk. The lack of vendor response and absence of patches exacerbate the threat, potentially leading to prolonged exposure and exploitation opportunities.

Summary

CVE-2026-4170 is an OS command injection vulnerability identified in Topsec TopACM version 3.0, affecting the HTTP request handler component located at /view/systemConfig/management/nmc_sync.php. The vulnerability stems from insufficient input validation and sanitization of the 'template_path' parameter, which can be manipulated by an unauthenticated remote attacker to execute arbitrary operating system commands on the affected server. This type of vulnerability allows attackers to gain control over the underlying system, potentially leading to unauthorized data access, system disruption, or pivoting to other internal resources. The exploit code has been publicly disclosed, increasing the risk of exploitation by malicious actors. The vendor was notified early but has not issued any response or patch, leaving systems exposed. The vulnerability does not require any authentication or user interaction, making it highly exploitable over the network. The CVSS v4.0 score is 9.3, indicating a critical severity level due to the combination of remote exploitability, no required privileges, and high impact on confidentiality, integrity, and availability. No mitigations or patches have been officially released, and the affected version is specifically TopACM 3.0.

References

Community reviews

Loading reviews…