CVE-2026-75348

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

GHSA-h42x-559x-q66g ↗EUVD-2026-95900 ↗

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

description

OpENer v2.3 and master through commit 76b95cf are affected in the EtherNet/IP TCP SendRRData Common Packet Format parser. A remote attacker can trigger a denial of service when the parser handles recognized optional socket-address items with insufficient packet data.

mitigation

No fixed version is recorded. Restrict EtherNet/IP TCP access to trusted networks and filter untrusted SendRRData traffic until an upstream update 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.
0.51%41st percentile
agent run time
15m
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-75348

{
  "etk_id": "ETK-2026-1123",
  "cve_id": "CVE-2026-75348",
  "display_id": "CVE-2026-75348",
  "ghsa_id": "GHSA-h42x-559x-q66g",
  "euvd_id": "EUVD-2026-95900",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds read in OpENer EtherNet/IP packet parser",
  "summary": "OpENer v2.3 and master through commit 76b95cf are affected in the EtherNet/IP TCP SendRRData Common Packet Format parser. A remote attacker can trigger a denial of service when the parser handles recognized optional socket-address items with insufficient packet data.",
  "mitigation": "No fixed version is recorded. Restrict EtherNet/IP TCP access to trusted networks and filter untrusted SendRRData traffic until an upstream update is available.",
  "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.0051,
  "epss_percentile": 0.4195,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.686846266666667,
  "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-75348"
    }
  }
}

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.