Skip to content
Applications

CVE-2026-32862

8.5
High
EPSS 0.15%Patch availableApr 8, 2026

Memory corruption in NI LabVIEW allows RCE after opening crafted VI file.

common questions

Is CVE-2026-32862 being exploited?

Not confirmed. CVE-2026-32862 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.15% probability of exploitation in the next 30 days.

How severe is CVE-2026-32862?

CVE-2026-32862 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-32862?

Yes. A fix has been recorded for CVE-2026-32862. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-32862 affect?

CVE-2026-32862 affects NI LabVIEW 2026 Q1 (26.1.0) and earlier. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-32862?

Monitor vendor advisories; plan upgrade when fixed; restrict opening untrusted VI files

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
NI LabVIEW 2026 Q1 (26.1.0) and earlier
impact

Memory corruption could lead to arbitrary code execution or data disclosure via a crafted VI file, requiring user interaction.

action required

Monitor only

affected versions
NI LabVIEW
  • affected< 23.0.0
  • affected>= 23.1.0 and < 23.3.9
  • affected>= 24.1.0 and < 24.3.6
  • affected>= 25.1.0 and < 25.3.4
  • affected>= 26.1.0 and < 26.1.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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free