Quick answers
- Is CVE-2026-68907 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-68907 being exploited in the wild.
- How severe is CVE-2026-68907?
- Informational severity, published 16 October 2026.
- Which products and versions are affected?
- MZ Automation libIEC61850 before 1.6.2.
- Is there a fix for CVE-2026-68907?
- Yes: fixed in 1.6.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-68907 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-68907?
- Check whether you run MZ Automation libIEC61850 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.6.2
Technical details
An off-by-one argument swap in checkDataSetAccess causes StringUtils_copyStringToBuffer to read from uninitialized stack memory (dataSetRef[130]) as a source string, then copies the over-read bytes into the caller's listName buffer. The vulnerability is triggered via remote MMS defineNamedVariableList requests on association or VMD-specific datasets; no authentication is required. While stack corruption is possible, the primary confirmed impact is denial of service through server crash.
Affected products
- mz-automation libIEC61850 before 1.6.2
Timeline
- 2026-10-16: disclosed