# CVE-2026-92210: NoMachine nxhtd Server-Side Request Forgery Information Disclosure Vulnerability


- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-q2x4-8x2v-f9cr

## What is CVE-2026-92210?

CVE-2026-92210 is a high-severity vulnerability in NoMachine, published on 21 Oct 2026. 

### Official description

NoMachine nxhtd Server-Side Request Forgery Information Disclosure Vulnerability. This vulnerability allows remote attackers to initiate arbitrary server-side requests on affected installations of NoMachine. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the web service, which listens on UDP port 4443 by default. The issue results from the lack of proper validation of a URI prior to accessing resources. An attacker can leverage this vulnerability to initiate requests in the context of the service account. Was ZDI-CAN-31619.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-92210 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92210 is a high-severity vulnerability in NoMachine, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-92210 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-92210/ (Markdown: https://insights.sbomify.com/CVE-2026-92210/index.md)
```

## Sources

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

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