CVE-2026-108893

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

GHSA-3px7-h6cw-5c93 ↗EUVD-2026-97438 ↗

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.
linksys E1700 1.0.0.4.003
ETK-2026-1384Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 11h 53msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h12m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Linksys E1700 devices running firmware through 1.0.0.4.003 are affected by a stack-based buffer overflow in a VLAN configuration handler. A remote attacker able to reach the device management interface may be able to trigger memory corruption through that handler.

mitigation

Do not expose the router management interface to untrusted networks; restrict it to trusted administrative hosts or a dedicated management network. Check for and apply a vendor firmware update if one becomes available, as no fixed version is identified in the evidence.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.53%43rd percentile
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 13:45Z
Δ 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-12 13:45Z
    ghsa: trigger signal, started the run
  2. 2026-10-12 13:45Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1384",
  "cve_id": "CVE-2026-108893",
  "display_id": "CVE-2026-108893",
  "ghsa_id": "GHSA-3px7-h6cw-5c93",
  "euvd_id": "EUVD-2026-97438",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stack buffer overflow in Linksys E1700 setVlan handler",
  "summary": "Linksys E1700 devices running firmware through 1.0.0.4.003 are affected by a stack-based buffer overflow in a VLAN configuration handler. A remote attacker able to reach the device management interface may be able to trigger memory corruption through that handler.",
  "mitigation": "Do not expose the router management interface to untrusted networks; restrict it to trusted administrative hosts or a dedicated management network. Check for and apply a vendor firmware update if one becomes available, as no fixed version is identified in the evidence.",
  "vendor": "linksys",
  "product": "E1700",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.0.0.4.003"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "E1700",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": 0.0053,
  "epss_percentile": 0.4387,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.700958983333333,
  "t0_at": "2026-10-12T13:45:15.796000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T13:45:15.796000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T13:45:15.796000+00:00",
      "url": "https://github.com/advisories/GHSA-3px7-h6cw-5c93"
    }
  }
}

published 2026-10-12 16:41Z
last change 2026-10-21 04:45Z

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.