Finding and attribution
The product of UA_Variant array dimensions can overflow during validation, leading to an out-of-bounds write/read condition. The two CVEs appear on one Anthropic CVD finding and are recorded as a single root issue. The public finding is static-analysis-only and lacks an attached reproducer.
Product: open62541 OPC UA stack. AI system: Claude Mythos Preview. Team / organization: Anthropic.
CVE identifiers: CVE-2026-63559, CVE-2026-65423.
AI and human contribution (source account): The individual Anthropic CVD page explicitly attributes this issue to Claude Mythos Preview and says Trail of Bits disclosed it to the maintainer.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: CVE source data reports publication July 30, 2026; Anthropic’s finding became public in its August 26 snapshot. No zero-day or exploitation assertion.
Remediation status: fix documented. The upstream open62541 fix is included in 1.3.19, 1.4.18 and 1.5.6 according to the vendor-linked CISA advisory data; retain the affected-version distinctions in that notice.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 30 Jul 2026. AI attribution dated 26 Aug 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: High · highest recorded score 8.8. Documented technical effects: data disclosure, other.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-63559: CVSS 3.1 · 7.5 (High) ·
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N· Assessment scenarios: GENERAL. icscert (CNA; CVE Program record) · checked 16 Nov 2026. - CVE-2026-63559: CVSS 4.0 · 8.7 (High) ·
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· Assessment scenarios: GENERAL. icscert (CNA; CVE Program record) · checked 16 Nov 2026. - CVE-2026-65423: CVSS 3.1 · 8.8 (High) ·
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H· Assessment scenarios: GENERAL. icscert (CNA; CVE Program record) · checked 16 Nov 2026. - CVE-2026-65423: CVSS 4.0 · 8.7 (High) ·
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N· Assessment scenarios: GENERAL. icscert (CNA; CVE Program record) · checked 16 Nov 2026.
CVE-2026-63559: data disclosure.
Prerequisites / affected scope: A remote attacker triggers the arrayDimensions integer overflow; the CNA says out-of-bounds heap read may potentially disclose sensitive information..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
CVE-2026-65423: other.
Prerequisites / affected scope: An integer overflow in the UA_Variant arrayDimensions product may let a remote attacker trigger an out-of-bounds write: attacker-controlled dimensions can wrap the product to match a small arrayLength, after which ranged writes access outside allocated bounds. CISA lists open62541 on Windows and Linux versions 1.3.0–1.3.17, 1.4.0–1.4.16, 1.5.0–1.5.4, and master as affected. This is the write-side CVE; CVE-2026-63559 separately documents an out-of-bounds heap read with possible sensitive-information disclosure. No RCE, DoS, or user-data alteration is established by the cited write description..
Exploitation evidence: CISA states that no known public exploitation specifically targeting these vulnerabilities had been reported at the time of the advisory.. Impact source · checked 16 Nov 2026.
Documented fix: The upstream open62541 fix is included in 1.3.19, 1.4.18 and 1.5.6 according to the vendor-linked CISA advisory data; retain the affected-version distinctions in that notice.