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

> A crafted IEC 60870-5-104 message triggers an out-of-bounds read in lib60870, potentially causing crashes or leaking memory.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/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:** 30 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-g3w7-x5rx-83xm, GHSA-gfjj-vr9m-mw6f, UBUNTU-CVE-2026-61893

## What is CVE-2026-61893?

CVE-2026-61893 is a medium-severity memory corruption vulnerability in MZ Automation lib60870, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A crafted IEC 60870-5-104 I-frame with TypeID 104 (C_TS_NA_1) and an 
inflated object count causes TestCommand_getFromBuffer to read one byte 
past the end of the heap-allocated message buffer.

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

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


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

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

## Is CVE-2026-61893 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61893 is a medium-severity memory corruption vulnerability in MZ Automation lib60870, published on 30 Jul 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-61893 exists.

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

## Sources

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

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