CVE-2026-44406
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 · uneditedZTE Cloud PC client uSmartView contains a DLL hijacking vulnerability; since uSmartViewServiceAgent.exe runs with SYSTEM privileges, successful hijacking enables local arbitrary code execution, privilege escalation, and memory corruption.contains a DLL hijacking vulnerability; since uSmartViewServiceAgent.exe runs with SYSTEM privileges, successful hijacking enables local arbitrary code execution, privilege escalation, and memory corruption.
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 · high confidenceZTE Cloud PC client uSmartView contains a DLL hijacking vulnerability in the uSmartViewServiceAgent.exe component. Since this service runs with SYSTEM privileges, an attacker who places a malicious DLL in a location where the service searches for DLLs can achieve arbitrary code execution with elevated privileges, resulting in privilege escalation from user level to SYSTEM and potential memory corruption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 7.23.20, < 7.25.43CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify ZTE Cloud PC client is installedLook for the uSmartView application or Zte Zxcloud Irai software on the system. Check common installation paths such as C:\Program Files\ZTE\uSmartView or C:\Program Files (x86)\ZTE\uSmartView. Also check the Windows installed programs list.Affected if The ZTE Cloud PC client uSmartView or Zte Zxcloud Irai software is present on the system
-
Identify installed versionLocate uSmartView or the Zxcloud Irai application, then check its version property. Common paths include the installation directory or look for version info in the Windows registry under the installed software entry.Affected if The installed version is greater than or equal to 7.23.20 and less than 7.25.43
-
Check if uSmartViewServiceAgent.exe existsSearch for the file uSmartViewServiceAgent.exe in the application installation directory. This is the vulnerable component that runs with elevated privileges.Affected if The uSmartViewServiceAgent.exe file exists in the uSmartView installation directory
-
Verify service is running with SYSTEM privilegesOpen Windows Services (services.msc), locate the uSmartViewServiceAgent service, right-click and select Properties, then check the Log On account. Alternatively, use command 'sc qc uSmartViewServiceAgent' or 'sc queryex uSmartViewServiceAgent' to check the service configuration.Affected if The service is configured to run under the LocalSystem account or other privileged account with SYSTEM-level access
-
Check DLL search path directories for write permissionsExamine the application directory and DLL search path of uSmartViewServiceAgent.exe for writable locations. Use accesschk.exe or icacls to check permissions on directories in the search order (application directory, system32, Windows, current working directory).Affected if Any directory in the DLL search path is writable by non-privileged users, allowing placement of a malicious DLL
A user is affected if ZTE Cloud PC client (Zte Zxcloud Irai) version 7.23.20 or higher but below 7.25.43 is installed with the uSmartViewServiceAgent.exe service running as SYSTEM and writable directories exist in its DLL search path.
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.
dbcve · scoped7.25.43
Apply the vendor patch from ZTE when available. As an interim measure, restrict write access to directories in the DLL search path and ensure the service runs with the minimum necessary privileges rather than SYSTEM.
7.25.43 or later
- Check current installed version of Zxcloud Irai/uSmartView on the affected system
- If version is >= 7.23.20 and < 7.25.43, the system is vulnerable
- Backup any critical data or configurations before upgrading
- Download the fixed version (7.25.43 or higher) from the official ZTE support portal at support.zte.com.cn
- Follow ZTE's standard upgrade procedure to update uSmartView to version 7.25.43 or later
- After upgrade, verify that uSmartViewServiceAgent.exe runs correctly and no unauthorized DLLs are loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44406 — 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-44406 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