CVE-2026-9869

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

GHSA-vh8v-g37q-6mg8 ↗EUVD-2026-105332 ↗

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.
Totolink TOTOLINK-X2000R-Gh-V1.0.0-B20250421.1327
ETK-2026-2272Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 00msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+6h44m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Totolink X2000R devices running firmware TOTOLINK-X2000R-Gh-V1.0.0-B20250421.1327 are affected by a stack buffer overflow in the Boa web-management request handler. An authenticated attacker able to reach the management HTTP service could execute code on the device.

mitigation

Restrict the device management HTTP interface to trusted administrator networks and accounts, and remove it from untrusted network exposure. Isolate affected devices until Totolink provides and you can apply a corrected firmware release.

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, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-20 20:25Z
Δ 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-20 20:25Z
    ghsa: trigger signal, started the run
  2. 2026-10-20 20:25Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2272",
  "cve_id": "CVE-2026-9869",
  "display_id": "CVE-2026-9869",
  "ghsa_id": "GHSA-vh8v-g37q-6mg8",
  "euvd_id": "EUVD-2026-105332",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stack buffer overflow in Totolink X2000R management handler",
  "summary": "Totolink X2000R devices running firmware TOTOLINK-X2000R-Gh-V1.0.0-B20250421.1327 are affected by a stack buffer overflow in the Boa web-management request handler. An authenticated attacker able to reach the management HTTP service could execute code on the device.",
  "mitigation": "Restrict the device management HTTP interface to trusted administrator networks and accounts, and remove it from untrusted network exposure. Isolate affected devices until Totolink provides and you can apply a corrected firmware release.",
  "vendor": "totolink",
  "product": "Totolink",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "TOTOLINK-X2000R-Gh-V1.0.0-B20250421.1327"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Totolink",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.759480316666666,
  "t0_at": "2026-10-20T20:25:21.253000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-20T20:25:21.253000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-20T20:25:21.253000+00:00",
      "url": "https://github.com/advisories/GHSA-vh8v-g37q-6mg8"
    }
  }
}

published 2026-10-21 02:54Z
last change 2026-10-21 03:59Z

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.