CVE-2026-75352

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

GHSA-fgff-hw4c-vx3q ↗EUVD-2026-95972 ↗

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

description

OpENer version 2.3 at commit 76b95cf is affected by an integer underflow in the server-side EtherNet/IP ForwardOpen connection-path parser. A remote attacker may cause a denial of service by reaching the affected service. Exposure requires the vulnerable EtherNet/IP service to be network-accessible.

mitigation

Restrict network access to the OpENer EtherNet/IP service to trusted hosts and segments. Apply an upstream update when a release containing a fix is available; the supplied evidence does not identify a fixed version.

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.33%24th percentile
agent run time
33m
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
    ghsa: trigger signal, started the run
  2. 2026-10-09 00:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2000",
  "cve_id": "CVE-2026-75352",
  "display_id": "CVE-2026-75352",
  "ghsa_id": "GHSA-fgff-hw4c-vx3q",
  "euvd_id": "EUVD-2026-95972",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Integer underflow in OpENer EtherNet/IP ForwardOpen parser",
  "summary": "OpENer version 2.3 at commit 76b95cf is affected by an integer underflow in the server-side EtherNet/IP ForwardOpen connection-path parser. A remote attacker may cause a denial of service by reaching the affected service. Exposure requires the vulnerable EtherNet/IP service to be network-accessible.",
  "mitigation": "Restrict network access to the OpENer EtherNet/IP service to trusted hosts and segments. Apply an upstream update when a release containing a fix is available; the supplied evidence does not identify a fixed version.",
  "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/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0033,
  "epss_percentile": 0.2497,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 33.44979525,
  "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://github.com/advisories/GHSA-fgff-hw4c-vx3q"
    }
  }
}

published 2026-10-18 18:28Z
last change 2026-10-21 11:38Z

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.