Skip to content
Applications

CVE-2026-18264

8.8
High
EPSS 1%Aug 22, 2026

Authenticated command-injection RCE in NoMachine web service (port 4000)

common questions

Is CVE-2026-18264 being exploited?

Not confirmed. CVE-2026-18264 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.2% probability of exploitation in the next 30 days.

How severe is CVE-2026-18264?

CVE-2026-18264 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-18264?

Not known from our data. No patch reference has been recorded for CVE-2026-18264, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-18264 affect?

CVE-2026-18264 affects NoMachine installations with web service (TCP 4000), NoMachine Enterprise/Desktop/Server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-18264?

Apply vendor patch when available; block/limit TCP 4000 and disable NoMachine web service until patched

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
NoMachine installations with web service (TCP 4000)NoMachine Enterprise/Desktop/Server
impact

Authenticated attacker can inject and execute system commands via the NoMachine web service, achieving remote code execution as the service account.

action required

Immediate action required

affected versions
NoMachine NoMachine
  • affected9.7.3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free