# CVE-2026-63559: o6 Automation open62541 Integer Overflow or Wraparound

> A remote attacker can exploit an integer overflow in open62541 to read out-of-bounds heap memory and disclose sensitive information.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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:** 25 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-63559, GHSA-6c97-xqf2-q99q, UBUNTU-CVE-2026-63559

## What is CVE-2026-63559?

CVE-2026-63559 is a high-severity vulnerability in o6 Automation open62541, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An integer overflow in the UA_Variant arrayDimensions product 
computation in open62541 may allow a remote attacker to read 
out-of-bounds heap memory, potentially disclosing sensitive information.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

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

## Is CVE-2026-63559 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63559 is a high-severity vulnerability in o6 Automation open62541, published on 30 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-63559 in the wild and no public exploit code.

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

## Sources

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

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