CVE-2026-92210

waiting for further signalsZero needs more public information before it can validate it.

GHSA-q2x4-8x2v-f9cr ↗EUVD-2026-107399 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
NoMachine nomachine_9.8.2_1_amd64.deb
ETK-2026-2353Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 10msince last run
47mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h54m
0
+2h
+6h
+8h
+10h
+12h

description

NoMachine nxhtd web-service deployments are affected by a server-side request forgery caused by insufficient URI validation. An unauthenticated remote attacker may cause the service to make requests using its service-account context. Exposure requires network access to the nxhtd web service, which uses port 4443 by default.

mitigation

Restrict network access to the nxhtd web-service port, including the default port 4443, to trusted clients only. Disable the NoMachine web interface where it is not required.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
47m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 17:16Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-21 17:16Z
    ghsa: trigger signal, started the run
  2. 2026-10-21 17:16Z

this entry in the feed

GET /api/v1/feed/CVE-2026-92210

{
  "etk_id": "ETK-2026-2353",
  "cve_id": "CVE-2026-92210",
  "display_id": "CVE-2026-92210",
  "ghsa_id": "GHSA-q2x4-8x2v-f9cr",
  "euvd_id": "EUVD-2026-107399",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated server-side request forgery in NoMachine nxhtd",
  "summary": "NoMachine nxhtd web-service deployments are affected by a server-side request forgery caused by insufficient URI validation. An unauthenticated remote attacker may cause the service to make requests using its service-account context. Exposure requires network access to the nxhtd web service, which uses port 4443 by default.",
  "mitigation": "Restrict network access to the nxhtd web-service port, including the default port 4443, to trusted clients only. Disable the NoMachine web interface where it is not required.",
  "vendor": "NoMachine",
  "product": "NoMachine",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "nomachine_9.8.2_1_amd64.deb"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "NoMachine",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 47.40455301666667,
  "t0_at": "2026-10-21T17:16:22.236000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T17:16:22.236000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T17:16:22.236000+00:00",
      "url": "https://github.com/advisories/GHSA-q2x4-8x2v-f9cr"
    }
  }
}

published 2026-10-21 20:22Z
last change 2026-10-21 22:02Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.