CVE-2026-75347

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

GHSA-cmxj-3q64-8hph ↗EUVD-2026-95916 ↗

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.
OpENer n/a
ETK-2026-1124Zero's internal tracking ID, independent of the CVE number., permanent identifier
11d 02h 29msince last run
7mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+26h18m
0
+2h
+4h
+6h
+8h
+10h

description

OpENer 2.3 and master revisions through 76b95cf are affected in Common Packet Format processing. A remote party able to reach the relevant EtherNet/IP service may be able to interrupt service through the pointer-lifetime flaw.

mitigation

Restrict access to OpENer EtherNet/IP services to trusted networks and peers, and monitor them for unexpected restarts or availability failures. Update to an upstream release or commit that addresses the issue when one is published.

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-1124",
  "cve_id": "CVE-2026-75347",
  "display_id": "CVE-2026-75347",
  "ghsa_id": "GHSA-cmxj-3q64-8hph",
  "euvd_id": "EUVD-2026-95916",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Expired pointer dereference in OpENer CPF handling",
  "summary": "OpENer 2.3 and master revisions through 76b95cf are affected in Common Packet Format processing. A remote party able to reach the relevant EtherNet/IP service may be able to interrupt service through the pointer-lifetime flaw.",
  "mitigation": "Restrict access to OpENer EtherNet/IP services to trusted networks and peers, and monitor them for unexpected restarts or availability failures. Update to an upstream release or commit that addresses the issue when one is published.",
  "vendor": null,
  "product": "OpENer",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AC:L/AV:N/A:H/C:N/I:N/PR:N/S:U/UI:N",
  "epss_score": 0.0042,
  "epss_percentile": 0.3518,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 6.973958416666667,
  "t0_at": "2026-10-09T00:00:00+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-09T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T00:00:00+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-75347"
    }
  }
}

published 2026-10-10 02:10Z
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.