CVE-2026-105284

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

EUVD-2026-92331 ↗

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-285 Improper Authorization
ETK-2026-639, permanent identifier
15d 19h 11msince last run
39mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h35m
0
+4h
+6h
+8h
+10h
+12h

description

Totolink A3002MU firmware 1.0.0-B20230403.1455 is affected by an authorization flaw in the authentication-check component. A remote attacker may obtain access or privileges that should be restricted; the advisory does not state any further precondition.

mitigation

Restrict management access to trusted networks, preferably through a VPN or firewall rules, and disable Internet-facing administration where possible. Monitor for and apply a vendor firmware update when one becomes available.

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.78%55th percentile
agent run time
39m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-05 09: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: 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:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-639",
  "cve_id": "CVE-2026-105284",
  "display_id": "CVE-2026-105284",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-92331",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in Totolink A3002MU authentication check",
  "summary": "Totolink A3002MU firmware 1.0.0-B20230403.1455 is affected by an authorization flaw in the authentication-check component. A remote attacker may obtain access or privileges that should be restricted; the advisory does not state any further precondition.",
  "mitigation": "Restrict management access to trusted networks, preferably through a VPN or firewall rules, and disable Internet-facing administration where possible. Monitor for and apply a vendor firmware update when one becomes available.",
  "vendor": "Totolink",
  "product": "A3002MU",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.0.0-B20230403.1455"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "A3002MU",
      "purl": null
    }
  ],
  "cwes": [
    285
  ],
  "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.0078,
  "epss_percentile": 0.5531,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 38.525633983333336,
  "t0_at": "2026-10-05T09:00:13.775000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-05T09:00:13.775000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T09:00:13.775000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-105284"
    }
  }
}

published 2026-10-05 09:56Z
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.