CVE-2026-68907

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

GHSA-7v2x-39mw-2979 ↗EUVD-2026-102911 ↗

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.
mz-automation libiec61850 = < 1.6.1
fixed in 1.6.2
CWE-125 Out-of-bounds Read
ETK-2026-1792Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 22h 53msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h45m
0
+4h
+6h
+8h
+10h
+12h

description

libiec61850 versions before 1.6.2 are affected by an out-of-bounds read in server-side dataset access processing. A remote attacker may cause an affected server to terminate when dynamic dataset support is enabled and a dataset access handler is configured.

mitigation

Upgrade libiec61850 to version 1.6.2 or later. Until upgrading, disable dynamic dataset support or remove the dataset access handler where operationally feasible.

fixed in 1.6.2

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.37%29th percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 15:48Z
Δ 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-16 15:48Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1792",
  "cve_id": "CVE-2026-68907",
  "display_id": "CVE-2026-68907",
  "ghsa_id": "GHSA-7v2x-39mw-2979",
  "euvd_id": "EUVD-2026-102911",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds read in libiec61850 dataset access",
  "summary": "libiec61850 versions before 1.6.2 are affected by an out-of-bounds read in server-side dataset access processing. A remote attacker may cause an affected server to terminate when dynamic dataset support is enabled and a dataset access handler is configured.",
  "mitigation": "Upgrade libiec61850 to version 1.6.2 or later. Until upgrading, disable dynamic dataset support or remove the dataset access handler where operationally feasible.",
  "vendor": "mz-automation",
  "product": "libiec61850",
  "affected": [
    {
      "affected_notes": [
        "= < 1.6.1"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "1.6.2"
      ],
      "package_name": "libiec61850",
      "purl": null
    }
  ],
  "cwes": [
    125
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0037,
  "epss_percentile": 0.2963,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.190917166666667,
  "t0_at": "2026-10-16T15:48:33.080000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T15:48:33.080000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T15:48:33.080000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-68907"
    }
  }
}

published 2026-10-16 17:21Z
last change 2026-10-21 16:15Z

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.