VulnerabilityPublished 27 Nov 2025Updated 28 Nov 2025

CVE-2025-66314: ZTE ElasticNet UME R32 · Improper Privilege Management

Affects ZTE ElasticNet UME R32Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.5High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Nov 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 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

AI-suggested

Monitor ZTE's official channels for patches or updates addressing CVE-2025-66314 and apply them immediately upon release.
Restrict network access to ElasticNet UME R32 management interfaces using firewalls and VPNs to limit exposure to trusted personnel and systems only.
Implement strict network segmentation to isolate management systems from general enterprise and internet-facing networks.
Conduct thorough access control reviews and audits to identify and remediate any misconfigurations or overly permissive ACLs within the ElasticNet environment.
Employ intrusion detection and prevention systems (IDS/IPS) with signatures or behavioral rules tailored to detect anomalous access attempts to ElasticNet UME R32.
Enforce strong authentication and authorization mechanisms around network management platforms, even if the product itself lacks them natively.
Train security teams to recognize signs of exploitation attempts and establish incident response plans specific to telecom management systems.
Consider deploying network-level anomaly detection to identify unusual traffic patterns indicative of exploitation attempts.
Engage with ZTE support and security advisories to stay informed about emerging threats and recommended best practices.
Document and test recovery procedures to minimize downtime and data loss in case of a breach.

Description

Improper Privilege Management vulnerability in ZTE ElasticNet UME R32 on Linux allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects ElasticNet UME R32: ElasticNet_UME_R32_V16.23.20.04.

Impact

For European organizations, especially telecom operators and enterprises utilizing ZTE ElasticNet UME R32, this vulnerability poses a significant risk to the confidentiality of sensitive network management data. Unauthorized access could lead to exposure of network configurations, subscriber information, or operational parameters, potentially facilitating further attacks or espionage. While integrity and availability are not directly impacted, the confidentiality breach alone can have severe regulatory and reputational consequences under GDPR and other data protection laws. The vulnerability's remote exploitability without authentication increases the attack surface, making it easier for threat actors to target European telecom infrastructure. This could disrupt trust in network services and complicate incident response efforts. Additionally, given the strategic importance of telecom infrastructure in Europe, exploitation could have cascading effects on critical communications and services. Organizations may face compliance penalties and loss of customer confidence if sensitive data is leaked. The absence of known exploits currently provides a window for proactive mitigation, but the high severity score indicates urgent attention is required.

CWE-269Improper Privilege Management (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Follow the principle of least privilege when assigning access rights to entities in a software system.
Architecture and Design · Separation of Privilege
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Restful Privilege Elevation (opens in a new tab)
Privilege Abuse (opens in a new tab)
Privilege Escalation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.zte.com.cn/zte-iccp-isupport-webui/bulletin/detail/2180460616364429350 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Dec 2025, 04:28 UTC

WeaknessesCWE-269

Technical details

References

Community reviews

Related threats