Home › Intelligence › Brief
VULNERABILITY BRIEF 🟠 High Vulnerability

Critical Remote Code Execution (CVE-2026-18264) in NoMachine’s getstat Service Threatens Enterprise Remote Access

A newly disclosed CVE‑2026‑18264 in NoMachine’s getstat command allows authenticated attackers to execute arbitrary code via the web service on TCP 4000. The flaw impacts all NoMachine installations that expose the service, prompting immediate patching. For SOC 2‑aligned organizations, the vulnerability underscores the need for robust access controls and continuous evidence of vendor patch management.

Verisq™ Intelligence · 📅 July 30, 2026 · 📰 zerodayinitiative.com
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
4 recommended
📰
Source
zerodayinitiative.com

Critical Remote Code Execution (CVE‑2026‑18264) in NoMachine’s getstat Service Threatens Enterprise Remote Access

What It Is — NoMachine’s web service (listening on TCP 4000 by default) fails to validate a user‑supplied string before invoking a system call, allowing an authenticated attacker to inject commands and execute arbitrary code in the context of the service account.

Exploitability — CVSS 8.8 (High). Exploitable with valid credentials; proof‑of‑concept disclosed; vendor has issued a patch.

Affected Products — All NoMachine client/server installations that expose the getstat endpoint.

Why It Matters for Compliance & Audit Readiness

  • Exposes a control‑gap that conflicts with SOC 2 access‑control criteria (CC6.1, CC6.2) requiring strict input validation and privileged‑access safeguards.
  • Underscores the need for continuous vendor‑risk monitoring and documented patch‑management as audit evidence.
  • Provides a concrete example for control‑mapping exercises, enabling organizations to capture remediation steps in a Trust Center‑ready audit trail.

Recommended Actions

  1. Apply NoMachine’s security update (KB TR06X11869) immediately.
  2. Restrict or disable port 4000 if the service is not required.
  3. Amend SOC 2 access‑control policies to enforce input validation for third‑party services.
  4. Log patch deployment and configuration changes in your compliance evidence repository.

Source: Zero Day Initiative Advisory

📰 Original Source
http://www.zerodayinitiative.com/advisories/ZDI-26-483/ ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →