VulnerabilityPublished 11 Mar 2026

CVE-2026-3943: H3C ACG1000-AK230 · Command Injection

Affects H3C ACG1000-AK230Source CVE Database V5

Compare

Public exploit available · 40% EPSS · CVSS 6.9 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 40.7% chance of exploitation in 30 days – higher than 98% 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:L/VI:L/VA:L/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: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
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 11 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
H3CACG1000-AK230	Affected =20260227	Fixed in–

AI-suggested

Until an official patch is released by H3C, organizations should implement the following mitigations: 1) Restrict network access to the management interface of the ACG1000-AK230 devices using firewalls or access control lists to limit exposure to trusted IP addresses only. 2) Monitor network traffic for unusual or suspicious requests targeting the /webui/?aaa_portal_auth_local_submit endpoint, employing intrusion detection/prevention systems with custom signatures for command injection patterns. 3) Disable or restrict web interface access if possible, or isolate the device management network segment from untrusted networks. 4) Regularly audit device configurations and logs for signs of compromise or unauthorized command execution. 5) Prepare for rapid deployment of vendor patches by maintaining an up-to-date inventory of affected devices and testing patch procedures in advance. 6) Educate network administrators about the vulnerability and encourage vigilance against phishing or social engineering that could facilitate exploitation. These targeted measures go beyond generic advice by focusing on limiting attack surface and early detection specific to this vulnerability.

Description

A vulnerability was found in H3C ACG1000-AK230 up to 20260227. This affects an unknown part of the file /webui/?aaa_portal_auth_local_submit. The manipulation of the argument suffix results in command injection. The attack can be launched remotely. The exploit has been made public and could be used. The vendor is investigating and remediating this issue.

Impact

The exploitation of CVE-2026-3943 can have severe consequences for organizations deploying the H3C ACG1000-AK230 device. Successful command injection can lead to full compromise of the device, allowing attackers to execute arbitrary commands, potentially gaining control over network traffic, intercepting sensitive data, or disrupting network services. This can result in confidentiality breaches, integrity violations, and denial of service conditions. Given the device's role in network access control and authentication, attackers could pivot to internal networks, escalate privileges, or establish persistent footholds. The remote and unauthenticated nature of the exploit increases the risk of widespread attacks, especially if exploit code is integrated into automated attack tools. Organizations relying on these devices for critical network functions may face operational disruptions, data loss, and reputational damage if the vulnerability is exploited.

Summary

CVE-2026-3943 is a remotely exploitable command injection vulnerability found in the H3C ACG1000-AK230 device firmware up to version 20260227. The vulnerability exists in the web interface endpoint /webui/?aaa_portal_auth_local_submit, specifically in the handling of the 'suffix' argument. Due to insufficient input validation or sanitization, an attacker can inject arbitrary system commands that the device executes with the privileges of the web server process. This flaw does not require authentication or user interaction, making it highly accessible to remote attackers. The vulnerability could allow attackers to compromise the device fully, potentially leading to unauthorized access, data leakage, or disruption of network services. Although the exploit code has been publicly released, there are no confirmed reports of active exploitation in the wild. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and partial impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). This vulnerability is significant due to the critical role of ACG1000-AK230 devices in network infrastructure, especially in enterprise and service provider environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Mar 2026, 19:17 UTC

Technical details

References

Community reviews

Related threats