CVE-2026-129971

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

EUVD-2026-131077 ↗

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.
Moxa ioLogik E1200 Series >= 1.0, <= 4.0
CWE-120 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
ETK-2026-5017Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 19msince last run
6mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h39m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Moxa ioLogik E1200 Series devices are affected by a buffer overflow in their SNMP service. A remote unauthenticated attacker may disrupt an affected device when they can reach its SNMP interface.

mitigation

Disable SNMP where it is not required, or restrict SNMP access to trusted management hosts and networks. No fixed version is recorded; limit network exposure until vendor remediation is 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.
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.
–
agent run time
6m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-20 06:51Z
Δ 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-20 06:51Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-5017",
  "cve_id": "CVE-2026-129971",
  "display_id": "CVE-2026-129971",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-131077",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SNMP buffer overflow in Moxa ioLogik E1200 Series",
  "summary": "Moxa ioLogik E1200 Series devices are affected by a buffer overflow in their SNMP service. A remote unauthenticated attacker may disrupt an affected device when they can reach its SNMP interface.",
  "mitigation": "Disable SNMP where it is not required, or restrict SNMP access to trusted management hosts and networks. No fixed version is recorded; limit network exposure until vendor remediation is available.",
  "vendor": "Moxa",
  "product": "ioLogik E1200 Series",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.0, <= 4.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "ioLogik E1200 Series",
      "purl": null
    }
  ],
  "cwes": [
    120
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 5.5468897,
  "t0_at": "2026-11-20T06:51:04.716000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-20T06:51:04.716000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-20T06:51:04.716000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-129971"
    }
  }
}

published 2026-11-20 07:24Z
last change 2026-11-20 08:30Z

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.