CVE-2026-40004
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 exists an openssl.cnf privilege escalation vulnerability in ZTE Cloud PC client uSmartview. An attacker can execute arbitrary code locally and escalate privileges.
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 confidenceThis is a local privilege escalation vulnerability in ZTE's uSmartview Cloud PC client. The vulnerability stems from an insecure openssl.cnf configuration that allows an attacker with local access to execute arbitrary code with elevated privileges. The CVSS 7.8 score indicates a local attack vector requiring low privileges but achieving high impact on system integrity.
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.
-
Identify if ZTE uSmartview Cloud PC client is installedCheck for the presence of uSmartview or Zxcloud Irai software on the system. Look for installation directories (commonly under C:\Program Files\ZTE or C:\Program Files (x86)\ZTE) or check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for ZTE entries.Affected if The software is present on the system
-
Determine the installed version of Zxcloud IraiCheck the version of the installed ZTE software. Right-click the uSmartview executable, select Properties, and view the Details tab for version information. Alternatively, query the Windows registry or check the uninstall entry for the version number.Affected if The version is 7.23.20 or higher but lower than 7.25.43 (7.23.20 <= version < 7.25.43)
-
Locate the openssl.cnf configuration fileFind the openssl.cnf file used by the uSmartview application. Common locations include the application installation directory, system OpenSSL directories, or the user's AppData folder. Check both the application directory and system OpenSSL paths.Affected if The openssl.cnf file exists in or alongside the uSmartview installation directory
-
Inspect openssl.cnf for insecure privilege escalation settingsOpen the openssl.cnf file in a text editor and examine the configuration for settings that could allow privilege escalation. Look for any custom OpenSSL engine configurations, extension handling, or policy settings that permit loading arbitrary libraries or executing code during certificate processing.Affected if The openssl.cnf contains configuration that permits privilege escalation (settings allowing arbitrary code execution or library loading during certificate operations)
-
Verify service privilege contextCheck if the uSmartview service runs with elevated privileges or under a high-privilege system account. Use Windows Services management console (services.msc) or run 'sc qc uSmartviewService' to examine the service logon account.Affected if The uSmartview service runs under a privileged account (such as SYSTEM, LocalSystem, or Administrator) and the openssl.cnf is writable or contains insecure settings
A user is affected if Zxcloud Irai version 7.23.20 through 7.25.42 is installed and the openssl.cnf configuration used by uSmartview contains insecure settings that could be exploited for local privilege escalation.
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
Organizations should update uSmartview to the latest patched version provided by ZTE and review openssl.cnf configuration files for insecure settings that could permit privilege escalation.
Zxcloud Irai version 7.25.43 or later
- Check current installed version of Zxcloud Irai (uSmartview) to confirm it is >= 7.23.20 and < 7.25.43
- Navigate to the official ZTE support portal at support.zte.com.cn
- Locate the Zxcloud Irai or uSmartview download section
- Download version 7.25.43 or the latest available version >= 7.25.43
- Close any running instances of the Zxcloud Irai client
- Install the updated version, ensuring the installation path does not contain untrusted directories
- Restart the client and verify the application runs without errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40004 — 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-40004 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