# CVE-2026-61378: AutomationDirect Productivity Suite Divide By Zero

> A local attacker can cause a system crash in AutomationDirect Productivity Suite via a divide-by-zero error, impacting industrial automation availability.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **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:** 16 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-22g8-27fc-wwmw

## What is CVE-2026-61378?

CVE-2026-61378 is a medium-severity denial of service vulnerability in AutomationDirect Productivity Suite, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A divide-by-zero vulnerability in the Productivity Suite allows a local 
attacker to cause a division by zero leading to a system crash.

Weakness: CWE-369 (Divide By Zero)

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


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

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

## Is CVE-2026-61378 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61378 is a medium-severity denial of service vulnerability in AutomationDirect Productivity Suite, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61378 in the wild and no public exploit code.

Affected product: AutomationDirect Productivity Suite. 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-61378/ (Markdown: https://insights.sbomify.com/CVE-2026-61378/index.md)
```

## Sources

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

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