# CVE-2026-19108: MZ Automation libiec61850 URCB Revalidation reporting.c deleteDataSetValuesShadowBuffer use after free

> A local attacker can exploit a use-after-free flaw in libiec61850 to potentially execute code or cause a 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:** 6 Aug 2026
- **Updated:** 8 Aug 2026
- **Also known as:** GHSA-c2h4-j5j4-67wf

## What is CVE-2026-19108?

CVE-2026-19108 is a medium-severity use after free vulnerability in MZ Automation libiec61850, published on 6 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in MZ Automation libiec61850 up to 1.6.1. The affected element is the function deleteDataSetValuesShadowBuffer of the file src/iec61850/server/mms_mapping/reporting.c of the component URCB Revalidation. The manipulation results in use after free. The attack needs to be approached locally. The exploit has been made public and could be used. Upgrading to version 1.6.2 is sufficient to fix this issue. The patch is identified as 486fd57f3aed65bb9d636ff00f9ddce2e450b168. Upgrading the affected component is advised.

Weakness: CWE-416 (Use After Free), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-19108 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19108 is a medium-severity use after free vulnerability in MZ Automation libiec61850, published on 6 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-19108 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-19108/ (Markdown: https://insights.sbomify.com/CVE-2026-19108/index.md)
```

## Sources

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

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