Quick answers
- Is CVE-2026-92210 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92210 being exploited in the wild.
- How severe is CVE-2026-92210?
- High severity, with a CVSS score of 7.2, published 21 October 2026.
- Which products and versions are affected?
- Nomachine versions before 8.27.1, 9.9.6, and 10.1.7.
- Is there a fix for CVE-2026-92210?
- Yes: fixed in NoMachine v8.27.1, v9.9.6, v10.1.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92210 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-92210?
- Check whether you run Nomachine at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: NoMachine v8.27.1, v9.9.6, v10.1.7
Technical details
A server-side request forgery (SSRF) vulnerability exists in the nxhtd web service due to insufficient validation of URIs before accessing resources. The flaw is network-accessible without authentication (AV:N/PR:N/UI:N) and allows an attacker to initiate arbitrary requests in the service account context, leading to information disclosure and potential integrity impact.
Affected products
- NoMachine NoMachine versions before 8.27.1, 9.9.6, and 10.1.7
Timeline
- 2026-08-07: disclosed: Vulnerability reported to vendor
- 2026-09-16: advisory: Coordinated public release of advisory
- 2026-09-16: patched: Fixed in NoMachine v8.27.1, v9.9.6, v10.1.7