# CVE-2026-16002: Out-of-bounds Read in MZ Automation lib60870

> An out-of-bounds read in lib60870 allows attackers to crash the parsing process, causing a denial of service in ICS environments.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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

## What is CVE-2026-16002?

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

### Official description

The affected product is vulnerable to an Out-of-bounds read, which may allow an attacker to crash the parsing process and cause a denial of service.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-16002 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16002 is a high-severity denial of service vulnerability in MZ Automation lib60870, 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-16002 in the wild and no public exploit code.

Affected product: MZ Automation lib60870. 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-16002/ (Markdown: https://insights.sbomify.com/CVE-2026-16002/index.md)
```

## Sources

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

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