# CVE-2026-18582: Memory corruption in libiec61850

> Remote attackers can trigger a memory corruption vulnerability in the libiec61850 library, potentially causing denial of service or arbitrary code execution.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-vj8r-wqrg-59qf

## What is CVE-2026-18582?

CVE-2026-18582 is a medium-severity memory corruption vulnerability in mz-automation libiec61850, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security flaw has been discovered in mz-automation libiec61850 up to 1.6.1. This vulnerability affects the function Reporting_RCBWriteAccessHandler of the file src/iec61850/server/mms_mapping/reporting.c of the component Report Sending Path Handler. The manipulation results in free of memory not on the heap. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. Upgrading to version 1.6.2 is able to resolve this issue. The patch is identified as 5b2a69f44256b8548927d8afdd7ac5f5381abe1e. It is suggested to upgrade the affected component. The vendor was contacted early about this disclosure.

Weakness: CWE-590 (Free of Memory not on the Heap)

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


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

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

## Is CVE-2026-18582 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18582 is a medium-severity memory corruption vulnerability in mz-automation libiec61850, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18582 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-18582/ (Markdown: https://insights.sbomify.com/CVE-2026-18582/index.md)
```

## Sources

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

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