Quick answers
- Is CVE-2026-92208 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92208 being exploited in the wild.
- How severe is CVE-2026-92208?
- High severity, with a CVSS score of 8.8, published 21 October 2026.
- Which products and versions are affected?
- Nomachine before 10.1.7, 9.9.6, and 8.27.1.
- Is there a fix for CVE-2026-92208?
- 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-92208 attacked?
- It is attacked from the adjacent network, in a hosted service.
- Am I affected by CVE-2026-92208?
- 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 v10.1.7, v9.9.6, v8.27.1
Technical details
The vulnerability exists in the parsing of mDNS resource records where insufficient validation of user-supplied data length results in a heap-based buffer overflow. Attackers on the network-adjacent segment can trigger this by sending specially crafted mDNS packets; no authentication or user interaction is required. Successful exploitation grants arbitrary code execution in the context of the service account.
Affected products
- NoMachine NoMachine before 10.1.7, 9.9.6, and 8.27.1
Timeline
- 2026-08-07: disclosed: Vulnerability reported to vendor
- 2026-09-16: advisory: Coordinated public release of advisory