CVE-2026-40001
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThere is a local privilege escalation vulnerability in the ZTE PROCESS Guard service of the cloud computer client, which may allow local arbitrary code execution, privilege escalation and path traversal bypass.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA local privilege escalation vulnerability exists in the ZTE PROCESS Guard service of the cloud computer client. The flaw allows a local attacker to achieve arbitrary code execution and privilege escalation by bypassing path traversal restrictions in the service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ZTE cloud computer client installationCheck for ZTE cloud computer client software in program directories or installed programs list (commonly in C:\Program Files\ZTE or C:\Program Files (x86)\ZTE)Affected if ZTE cloud computer client is installed on the system
-
Locate PROCESS Guard serviceOpen Windows Services (services.msc) or run 'sc query' command and search for a service named 'PROCESS Guard' or similar ZTE-related guard/protection serviceAffected if A PROCESS Guard service related to ZTE cloud computer client is present and running
-
Verify service executable pathRight-click the PROCESS Guard service, select Properties, and examine the 'Path to executable' field for any signs of path traversal patterns (multiple backslashes, ../ sequences, or unusual path components)Affected if The service executable path contains suspicious traversal patterns or unusual path configurations
-
Check service file permissionsUse icacls or Explorer security properties on the PROCESS Guard service executable to examine if low-privilege users have write access to the service directory or executableAffected if Non-admin users have write permissions to the service executable or its directory, allowing path traversal exploitation
-
Inspect service configurationRun 'sc qc PROCESS_GUARD' (or the actual service name) to query the service configuration and check for any binary path anomaliesAffected if The service binary path shows evidence of path manipulation or unusual parameters
A user is affected if the ZTE cloud computer client with PROCESS Guard service is installed and the service has exploitable file permissions or path configuration weaknesses.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict PROCESS Guard service permissions, implement strict path validation to prevent traversal attacks, and apply vendor-provided patches for the cloud computer client.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-40001 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data