LiveActive security incident?Get immediate response
CVE Record

CVE-2026-49003: Unauthenticated RCE Vulnerability in ZTE ZXDU68 S202 V5.0 Product

Attackers can exploit command injection vulnerabilities to delete core system runtime files, causing the monitoring module to crash and become paralyzed; simultaneously, they can obtain root privileges to steal configuration passwords such as SNMP, thereby tampering with critical system parameters and triggering abnormal operation of the entire power system.

CriticalCVSS 9.6Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

An unauthenticated attacker with adjacent-network access could take control of affected ZTE power-system equipment. Reported impacts include crashing monitoring, stealing configuration credentials with root privileges, changing critical parameters, and disrupting power-system operation. The severity is critical because confidentiality, integrity, and availability can all be lost without user interaction.

Executive priority

Prioritize immediate identification and containment of reachable affected units, especially those supporting critical power operations. Assign operational-security and engineering owners jointly because remediation or isolation may affect availability. Escalate confirmed monitoring crashes, credential exposure, or parameter tampering as potential compromise indicators.

Technical view

CVE-2026-49003 affects specified ZXDU68 S202 V5.0R02M02 ACB builds V1.30.01.00 through V1.30.01.03. The record describes unauthenticated command injection leading to root-level access and file deletion. CVSS 3.1 is 9.6: adjacent access, low complexity, no privileges or interaction, changed scope, and high impact across all security properties.

Likely exposure

Exposure is limited to the four named builds and requires an adjacent-network path according to the CVSS vector. Organizations operating ZXDU68 S202 V5.0 should verify exact ACB versions and network reachability. The bundle identifies no CPEs and marks unspecified versions unaffected, so broader product exposure is not established.

Exploitation context

The supplied sources do not establish active exploitation, public exploit availability, or inclusion in CISA KEV. They describe a plausible unauthenticated compromise path with root access and operational disruption. Treat reachable affected equipment as urgent while distinguishing technical severity from confirmed attacks in the wild.

Researcher notes

The source bundle labels this command injection and unauthenticated RCE but maps CWE-287, an authentication weakness; that classification mismatch remains unresolved. No vulnerable interface, protocol, patch identifier, detection signature, or exploitation evidence is supplied. Validation should remain non-destructive and focus on version, reachability, telemetry, and vendor guidance.

Mitigation direction

  • Check the ZTE advisory for an approved update or mitigation; the bundle names no specific fix.
  • Restrict affected equipment to trusted adjacent management networks and remove unnecessary access paths.
  • Isolate affected units where operationally safe until vendor-directed remediation is confirmed.
  • After containment, rotate exposed SNMP and configuration credentials using approved operational procedures.
  • Monitor critical parameters and power-system behavior for unauthorized or abnormal changes.

Validation and detection

  • Confirm the device model and exact ACB build against V1.30.01.00 through V1.30.01.03.
  • Map every adjacent-network path capable of reaching affected equipment.
  • Verify segmentation and access controls block unauthorized management traffic.
  • Review monitoring failures, runtime-file anomalies, credential access, and critical parameter changes.
  • Confirm any remediation directly against current ZTE guidance and retest defensive controls.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-287: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-49003 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.6 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.6CVSS 3.1CriticalCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H2.86zte

Vulnerability scoring details

Base CVSS 3.1 score

9.6Critical
CVSS 3.1 vector shape for CVE-2026-49003Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ZTEZXDU68 S202 V5.0ZXDU68 S202 V5.0R02M02 ACB V1.30.01.00 、ZXDU68 S202 V5.0R02M02 ACB V1.30.01.01、ZXDU68 S202 V5.0R02M02 ACB V1.30.01.02、ZXDU68 S202 V5.0R02M02 ACB V1.30.01.03unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-287 · source CWE mapping

CWE mapping pending import

This CVE carries a CWE mapping that will resolve to a full Glexia CWE intelligence page after the official CWE import is complete.