CVE-2026-105285

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

GHSA-x79h-v8f2-79c8 ↗EUVD-2026-92383 ↗

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 A3002MU 1.0.0-B20230403.1455
CWE-121 Stack-based Buffer Overflow
ETK-2026-641, permanent identifier
15d 19h 59msince last run
21mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h53m
0
+4h
+6h
+8h
+10h
+12h

description

Totolink A3002MU firmware 1.0.0-B20230403.1455 is affected by a stack-based buffer overflow in the QoS Rule Handler. A remote attacker may be able to trigger the flaw by submitting crafted QoS rule input to the affected endpoint; access to that management functionality is a precondition.

mitigation

Restrict access to the router management interface and QoS configuration functions to trusted administrative networks. Monitor the vendor 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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.64%49th percentile
agent run time
21m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-05 09:15Z
Δ 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: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-05 09:15Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-641",
  "cve_id": "CVE-2026-105285",
  "display_id": "CVE-2026-105285",
  "ghsa_id": "GHSA-x79h-v8f2-79c8",
  "euvd_id": "EUVD-2026-92383",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stack-based buffer overflow in Totolink A3002MU QoS Rule Handler",
  "summary": "Totolink A3002MU firmware 1.0.0-B20230403.1455 is affected by a stack-based buffer overflow in the QoS Rule Handler. A remote attacker may be able to trigger the flaw by submitting crafted QoS rule input to the affected endpoint; access to that management functionality is a precondition.",
  "mitigation": "Restrict access to the router management interface and QoS configuration functions to trusted administrative networks. Monitor the vendor for updated firmware, as no fixed version is recorded.",
  "vendor": "Totolink",
  "product": "A3002MU",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.0.0-B20230403.1455"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "A3002MU",
      "purl": null
    }
  ],
  "cwes": [
    121
  ],
  "cvss_score": 10,
  "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:H/SI:H/SA:H/E:P",
  "epss_score": 0.0064,
  "epss_percentile": 0.4995,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 20.699471533333334,
  "t0_at": "2026-10-05T09:15:15.881000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-05T09:15:15.881000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T09:15:15.881000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-105285"
    }
  }
}

published 2026-10-05 10:47Z
last change 2026-10-21 06:34Z

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.