Quick answers
- Is CVE-2026-92209 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92209 being exploited in the wild.
- How severe is CVE-2026-92209?
- High severity, with a CVSS score of 7.8, published 21 October 2026.
- Which products and versions are affected?
- NoMachine NoMachine.
- Is there a fix for CVE-2026-92209?
- Yes: fixed in NoMachine v10.1.7, v9.9.6, v8.27.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92209 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-92209?
- Check whether you run Nomachine. 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 v10.1.7, v9.9.6, v8.27.1
Technical details
The vulnerability stems from insufficient entropy in Redis credential generation within NoMachine's authentication mechanism. A local attacker who has already gained low-privilege code execution can exploit weak credentials to access the Redis database and escalate to service account privileges. The flaw allows arbitrary code execution in the context of the NoMachine service, providing a path from low-privilege user to full service compromise.
Affected products
- NoMachine NoMachine
Timeline
- 2026-07-29: disclosed: Vulnerability reported to vendor
- 2026-09-16: advisory: Coordinated public release of advisory