CVE-2026-97854

validatingZero is analyzing and reversing it now.

GHSA-8m66-f8m4-wc2j ↗EUVD-2026-112753 ↗

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.
Yamaha Corporation NWR100 <= Rev.26.00.07
CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
ETK-2026-2964Zero's internal tracking ID, independent of the CVE number., permanent identifier
16mrunning
patch analysiscurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0hvalidating
0
+1h
+2h

description

Yamaha NWR100 wireless LAN routers are affected by an OS command injection vulnerability. An attacker able to send requests to the affected interface may execute operating-system commands; Internet exposure depends on whether Web GUI access from the WAN has been enabled.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Disable WAN access to the NWR100 Web GUI and restrict management interfaces to trusted administrative networks. Apply vendor updates when Yamaha publishes a fixed release; no fixed version is recorded in the advisory.

check
building now
exploit
not yet
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.
–
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
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-29 11:33Z
Δ 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-10-29 11:33Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2964",
  "cve_id": "CVE-2026-97854",
  "display_id": "CVE-2026-97854",
  "ghsa_id": "GHSA-8m66-f8m4-wc2j",
  "euvd_id": "EUVD-2026-112753",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "OS command injection in Yamaha NWR100",
  "summary": "Yamaha NWR100 wireless LAN routers are affected by an OS command injection vulnerability. An attacker able to send requests to the affected interface may execute operating-system commands; Internet exposure depends on whether Web GUI access from the WAN has been enabled.",
  "mitigation": "Disable WAN access to the NWR100 Web GUI and restrict management interfaces to trusted administrative networks. Apply vendor updates when Yamaha publishes a fixed release; no fixed version is recorded in the advisory.",
  "vendor": "Yamaha Corporation",
  "product": "NWR100",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= Rev.26.00.07"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "NWR100",
      "purl": null
    }
  ],
  "cwes": [
    78
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 22.9821728,
  "t0_at": "2026-10-29T11:33:51.649000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-29T11:33:51.649000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T11:33:51.649000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-97854"
    }
  }
}

published 2026-10-29 11:43Z
last change 2026-10-29 13:13Z

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.