CVE-2026-78801

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

GHSA-5jmj-p7j2-pm54 ↗EUVD-2026-108205 ↗

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.
SKYWORTH SK-WR6640X Wi-Fi 6 Dual-Band Fiber Router (AX1800M) n/a
ETK-2026-2460Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 01msince last run
8mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+16h03m
0
+2h
+4h
+6h
+8h
+10h

description

SKYWORTH SK-WR6640X Wi-Fi 6 Dual-Band Fiber Router (AX1800M) firmware V1.0.3 is affected. A remote attacker may obtain sensitive information through an exposed router interface; the evidence does not state whether authentication is required.

mitigation

Restrict remote access to the router management interface and limit it to trusted administrative networks. Monitor vendor support channels for updated firmware, as no fixed version is recorded.

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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 00:00Z
Δ 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

No artifact: no remotely reachable path found.

source signals

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

  1. 2026-10-22 00:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2460",
  "cve_id": "CVE-2026-78801",
  "display_id": "CVE-2026-78801",
  "ghsa_id": "GHSA-5jmj-p7j2-pm54",
  "euvd_id": "EUVD-2026-108205",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Sensitive information exposure in SK-WR6640X router",
  "summary": "SKYWORTH SK-WR6640X Wi-Fi 6 Dual-Band Fiber Router (AX1800M) firmware V1.0.3 is affected. A remote attacker may obtain sensitive information through an exposed router interface; the evidence does not state whether authentication is required.",
  "mitigation": "Restrict remote access to the router management interface and limit it to trusted administrative networks. Monitor vendor support channels for updated firmware, as no fixed version is recorded.",
  "vendor": "SKYWORTH",
  "product": "SKYWORTH SK-WR6640X Wi-Fi 6 Dual-Band Fiber Router (AX1800M)",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.235127516666667,
  "t0_at": "2026-10-22T00:00:00+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T00:00:00+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-78801"
    }
  }
}

published 2026-10-22 15:54Z
last change 2026-10-22 17:30Z

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.