# CVE-2026-5053: NoMachine External Control of File Path Arbitrary File Deletion Vulnerability

> Local attackers can delete arbitrary files as root due to improper path validation in NoMachine, requiring prior low-privileged code execution.

- **Severity:** High 7.1 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-75gg-gxqp-fq44

## What is CVE-2026-5053?

CVE-2026-5053 is a high-severity path traversal vulnerability in NoMachine, published on 11 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NoMachine External Control of File Path Arbitrary File Deletion Vulnerability. This vulnerability allows local attackers to delete arbitrary files 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 handling of environment variables. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to delete files in the context of root. Was ZDI-CAN-28644.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-5053?

It affects 1 product.


Products: Nomachine Nomachine.

## How do I fix CVE-2026-5053?

No fix has been published for CVE-2026-5053 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5053 being exploited?

There is no known exploitation of CVE-2026-5053 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-5053: Writeup + PoC (github_poc): https://github.com/do4choo/CVE-2026-5053_NoMachine_LPE

## Other vulnerabilities in NoMachine

- [CVE-2018-0664](https://insights.sbomify.com/CVE-2018-0664/): Other in NoMachine App for Android (critical 9.8)
- [CVE-2023-39107](https://insights.sbomify.com/CVE-2023-39107/): Path traversal in n/a (critical 9.1)
- [CVE-2017-12763](https://insights.sbomify.com/CVE-2017-12763/): Privilege escalation in n/a (high 8.8)
- [CVE-2026-5054](https://insights.sbomify.com/CVE-2026-5054/): NoMachine External Control of File Path Local Privilege Escalation Vulnerability (high 7.8)
- [CVE-2026-5055](https://insights.sbomify.com/CVE-2026-5055/): NoMachine Uncontrolled Search Path Element Local Privilege Escalation Vulnerability (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5053 and fix it if it is affected.

What it is: CVE-2026-5053 is a high-severity path traversal vulnerability in NoMachine, published on 11 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5053 in the wild and no public exploit code.

Affected product: NoMachine. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5053/ (Markdown: https://insights.sbomify.com/CVE-2026-5053/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5053
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5053
- OSV: https://osv.dev/vulnerability/CVE-2026-5053

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5053/
Summaries are generated and may contain mistakes; the official description above is the record.