dbcve.org
NomachineApplication

CVE-2026-5055

HIGH · 7.8 CVSS v3.0 Published 2026-04-11
Fix available
A fix is available. Upgrade to 9.4.14 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
NoMachine Uncontrolled Search Path Element Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of NoMachine. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the NoMachine Device Server. The product loads a library from an unsecured location. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-28494.

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 confidence

This is a DLL hijacking/uncontrolled search path vulnerability in NoMachine Device Server. The application loads libraries from an unsecured location, allowing a local attacker with low-privileged code execution to place a malicious DLL that gets loaded by the privileged NoMachine service process, escalating privileges to SYSTEM context.

MitigationEnsure NoMachine loads libraries only from secure, trusted directories by using absolute paths, removing world-writable directories from the library search path, or implementing safe DLL loading mechanisms.

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
NomachineApplication
Affected:< 9.4.14

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify NoMachine installation and version
    Check the installed NoMachine version by reviewing version information in the NoMachine installation directory, or use system commands to query the installed package version (e.g., nxversion.txt in the installation folder, or system package manager).
    Affected if NoMachine is installed and the version is lower than 9.4.14 (e.g., 9.0.0, 8.0, 7.x, etc.)
  2. Identify NoMachine service account
    Check the NoMachine service properties in Windows Services (services.msc) or use 'sc query' or 'sc qc' commands to query the service configuration and identify the account under which the NoMachine Device Server service runs.
    Affected if The NoMachine service runs under the SYSTEM account, LocalSystem, or another high-privilege account rather than a low-privilege service account
  3. Check DLL search path for unsecured directories
    Inspect the NoMachine service process environment and DLL search order using tools like Process Explorer, Process Monitor, or by reviewing the service configuration. Look for directories in the PATH environment variable or working directory that are world-writable or located in user-accessible locations.
    Affected if The NoMachine service process loads DLLs from directories that are writable by low-privilege users (e.g., temp directories, user profile folders, or unprotected application subdirectories)
  4. Verify service binary location permissions
    Examine file system permissions on the NoMachine installation directory and its subdirectories. Check if low-privilege users can write files to directories from which NoMachine loads executable code or libraries.
    Affected if Low-privilege users have write access to directories within the NoMachine installation path from which the service loads DLLs or executables

You are affected if NoMachine version is below 9.4.14 AND the service runs with elevated privileges AND low-privilege users can place malicious DLLs in directories the service uses for library loading.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.4.14 or later
Fixed in 9.4.14
Interim mitigation

Ensure NoMachine loads libraries only from secure, trusted directories by using absolute paths, removing world-writable directories from the library search path, or implementing safe DLL loading mechanisms.

Recommended fix Moderate confidence

9.4.14 or later

  1. 1. Download NoMachine version 9.4.14 or later from the official NoMachine website (nomachine.com)
  2. 2. Ensure you have administrative privileges on the target system
  3. 3. Close any running NoMachine processes before upgrading
  4. 4. Install the updated NoMachine version following the standard installation procedure
  5. 5. Verify the installed version matches or exceeds 9.4.14
  6. 6. Restart any NoMachine services to ensure the updated components are loaded

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nomachine Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5055 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5055 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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