Quick answers
- Is CVE-2026-64203 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64203 being exploited in the wild.
- How severe is CVE-2026-64203?
- High severity, with a CVSS score of 7.8, published 25 August 2026.
- Which products and versions are affected?
- NI Labview 2026 Q3 (26.3.0) and prior.
- Is there a fix for CVE-2026-64203?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-64203 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-64203?
- Check whether you run NI Labview at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
CVE-2026-64203 is an out-of-bounds read vulnerability in the QualifiedName prepend function within NI LabVIEW. The vulnerability is triggered when a user opens a specially crafted VI file, requiring user interaction but no authentication or elevated privileges. An attacker can exploit this memory corruption to read sensitive information from process memory or execute arbitrary code with the privileges of the user running LabVIEW. The vulnerability affects LabVIEW 2026 Q3 (26.3.0) and all prior versions; patches are available through NI Update Service or NI Package Manager, with specific patch versions recommended for each release line (2026 Q3 Patch 1, 2025 Q3 Patch 5, 2024 Q3 Patch 7, 2023 Q3 Patch 10).
Affected products
- NI LabVIEW 2026 Q3 (26.3.0) and prior
Timeline
- 2026-08-25: disclosed