CVE-2026-64202
Memory corruption in NI LabVIEW allows code execution or data disclosure via crafted VI.
Is CVE-2026-64202 being exploited?
Not confirmed. CVE-2026-64202 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.
How severe is CVE-2026-64202?
CVE-2026-64202 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64202?
Yes. A fix has been recorded for CVE-2026-64202. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64202 affect?
CVE-2026-64202 affects NI LabVIEW 2026 Q3 (26.3.0) and earlier, LabVIEW VI files (.vi). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64202?
Apply vendor update when released; block/untrusted VIs and restrict user privileges.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Opening a malicious VI can cause information disclosure or arbitrary code execution under the victim's user context.
Patch when possible
- affected< 23.0.0
- affected>= 23.1.0 and < 23.3.10
- affected>= 24.1.0 and < 24.3.7
- affected>= 25.1.0 and < 25.3.5
- affected>= 26.1.0 and < 26.3.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.