# CVE-2026-19206: MZ Automation libiec61850 ASDU Element sv_subscriber.c SVReceiver_stopThreadless heap-based overflow

> A local attacker can trigger a heap-based buffer overflow in libiec61850, potentially leading to code execution or denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-72v3-v5v5-6xx3

## What is CVE-2026-19206?

CVE-2026-19206 is a medium-severity memory corruption vulnerability in MZ Automation libiec61850, published on 7 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security flaw has been discovered in MZ Automation libiec61850 up to 1.6.1. This affects the function SVReceiver_stopThreadless of the file src/sampled_values/sv_subscriber.c of the component ASDU Element Handler. Performing a manipulation results in heap-based buffer overflow. The attack must be initiated from a local position. The exploit has been released to the public and may be used for attacks. Upgrading to version 1.6.2 is able to mitigate this issue. The patch is named a96bd674e0238276dd1387d31d52e55229d0771e. The affected component should be upgraded.

Weakness: CWE-122 (Heap-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-19206?


## How do I fix CVE-2026-19206?

No fix has been published for CVE-2026-19206 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19206 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19206 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19206 and fix it if it is affected.

What it is: CVE-2026-19206 is a medium-severity memory corruption vulnerability in MZ Automation libiec61850, published on 7 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19206 exists.

Affected product: MZ Automation libiec61850. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19206/ (Markdown: https://insights.sbomify.com/CVE-2026-19206/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19206
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19206
- OSV: https://osv.dev/vulnerability/CVE-2026-19206

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19206/
Summaries are generated and may contain mistakes; the official description above is the record.
