# CVE-2026-60063: AutomationDirect Productivity Suite Out-of-bounds Write

> A local attacker can exploit an out-of-bounds write in AutomationDirect Productivity Suite via crafted IOCTL requests to achieve privilege escalation or cause system instability.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/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-7f5q-frx2-ggqg

## What is CVE-2026-60063?

CVE-2026-60063 is a high-severity memory corruption 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

An out-of-bounds write vulnerability in the Productivity Suite allows a 
local attacker to trigger kernel memory corruption via a crafted IOCTL 
request, potentially resulting in privilege escalation or system 
instability.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-60063 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60063 is a high-severity memory corruption 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-60063 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-60063/ (Markdown: https://insights.sbomify.com/CVE-2026-60063/index.md)
```

## Sources

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

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