# CVE-2026-50032: NULL Pointer Dereference in MZ Automation libIEC61850

> A network-adjacent attacker can crash the server by sending a malformed MMS WriteRequest with an empty data list.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-37jp-3q9w-phcm

## What is CVE-2026-50032?

CVE-2026-50032 is a high-severity vulnerability in MZ Automation libIEC61850, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A NULL pointer dereference in the MMS Write Named Variable List handler, which may allow a network adjacent attacker to crash the server by sending a WriteRequest with an empty listOfData field.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2026-50032 being exploited?

There is no known exploitation of CVE-2026-50032 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50032 is a high-severity vulnerability in MZ Automation libIEC61850, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50032 in the wild and no public exploit code.

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-50032/ (Markdown: https://insights.sbomify.com/CVE-2026-50032/index.md)
```

## Sources

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

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