CVE-2026-12487

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

GHSA-mwxv-c5g9-866v ↗EUVD-2026-126812 ↗

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.
Zyxel EE5301-00 customized firmware 5.63(ACLD.2)b3_D0
CWE-863 Incorrect Authorization
ETK-2026-4638Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 17h 55msince last run
24mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h59m
0
+4h
+6h
+8h
+10h
+12h

description

EE5301-00 customized firmware version 5.63(ACLD.2)b3_D0 has an authorization-control weakness in its SNMP functionality. An unauthenticated network attacker may be able to interrupt device availability when the SNMP service is reachable.

mitigation

Disable SNMP where it is not needed. Otherwise, limit SNMP access to trusted administrative networks and keep the service inaccessible from the internet.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.25%16th percentile
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-17 02: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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-17 02:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4638",
  "cve_id": "CVE-2026-12487",
  "display_id": "CVE-2026-12487",
  "ghsa_id": "GHSA-mwxv-c5g9-866v",
  "euvd_id": "EUVD-2026-126812",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SNMP authorization flaw in EE5301-00 customized firmware",
  "summary": "EE5301-00 customized firmware version 5.63(ACLD.2)b3_D0 has an authorization-control weakness in its SNMP functionality. An unauthenticated network attacker may be able to interrupt device availability when the SNMP service is reachable.",
  "mitigation": "Disable SNMP where it is not needed. Otherwise, limit SNMP access to trusted administrative networks and keep the service inaccessible from the internet.",
  "vendor": "Zyxel",
  "product": "EE5301-00 customized firmware",
  "affected": [
    {
      "affected_notes": [
        "5.63(ACLD.2)b3_D0"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "EE5301-00 customized firmware",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0025,
  "epss_percentile": 0.166,
  "epss_asof": "2026-11-17",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 24.181288633333335,
  "t0_at": "2026-11-17T02:00:25.389000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-17T02:00:25.389000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-17T02:00:25.389000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-12487"
    }
  }
}

published 2026-11-17 02:35Z
last change 2026-11-18 21:29Z

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.