Which versions of Labview are affected by CVE-2026-32862?

CVE-2026-32862 is a high-severity memory corruption vulnerability in National Instruments LabVIEW that enables arbitrary code execution when users open malicious VI files, affecting all versions…. A patch is available.

How to fix or mitigate CVE-2026-32862?

Within 24 hours: Identify all LabVIEW installations across engineering and operations teams via asset inventory; notify users not to open VI files from untrusted sources pending patch deployment. Within 7 days: Deploy vendor-released patch to all LabVIEW 2026 Q1 (26.1.0) and prior version installations; prioritize systems handling external or third-party VI files. Within 30 days: Confirm patch installation via vulnerability scanner; review file-sharing and collaboration workflows to enforce VI file source verification policies.

Labview CVE-2026-32862

Q: What is the CVSS score of CVE-2026-32862?

CVE-2026-32862 has a CVSS 4.0 base score of 8.5 (High). CVSS vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-19903 HIGH

Out-of-bounds Write (CWE-787)

2026-04-07 NI

GHSA-2hvj-57fv-jjcc

Memory Corruption Information Disclosure Buffer Overflow RCE Labview

8.5

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

8.5 HIGH

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Scope

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 06:02 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

26.1.1,24.3.6,25.3.4

EUVD ID Assigned

Apr 07, 2026 - 20:16 euvd

EUVD-2026-19903

Analysis Generated

Apr 07, 2026 - 20:16 vuln.today

CVE Published

Apr 07, 2026 - 19:50 nvd

HIGH 8.5

DescriptionCVE.org

There is a memory corruption vulnerability due to an out-of-bounds write in ResFileFactory::InitResourceMgr() in NI LabVIEW. This vulnerability may result in information disclosure or arbitrary code execution. Successful exploitation requires an attacker to get a user to open a specially crafted VI file. This vulnerability affects NI LabVIEW 2026 Q1 (26.1.0) and prior versions.

AnalysisAI

Memory corruption in NI LabVIEW's ResFileFactory::InitResourceMgr() function allows arbitrary code execution or information disclosure when users open malicious VI files. Affects LabVIEW 2026 Q1 (26.1.0) and all prior versions. CVSS 8.5 severity reflects high impact potential, though exploitation requires user interaction to open a crafted file. No public exploit identified at time of analysis, with EPSS data unavailable for this recently assigned CVE. Local attack vector limits remote exploitation scenarios.

Technical ContextAI

This vulnerability stems from an out-of-bounds write (CWE-787) in the ResFileFactory::InitResourceMgr() function within NI LabVIEW's resource file handling subsystem. LabVIEW VI (Virtual Instrument) files contain executable graphical code and embedded resources that must be parsed and initialized when opened. The ResFileFactory component manages resource initialization during VI file loading. The out-of-bounds write occurs during this initialization process, allowing memory corruption beyond allocated buffer boundaries. This class of vulnerability typically arises from insufficient bounds checking when processing untrusted file data structures, particularly during deserialization or resource allocation operations. The CPE identifier cpe:2.3:a:ni:labview:*:*:*:*:*:*:*:* indicates all LabVIEW versions through 26.1.0 contain vulnerable code in this resource management component, suggesting a long-standing architectural issue rather than a recent regression.

RemediationAI

Users should upgrade to the patched version of NI LabVIEW specified in the vendor security advisory at https://www.ni.com/en/support/security/available-critical-and-security-updates-for-ni-software/2026/memory-corruption-vulnerabilities-in-ni-labview.html. The advisory title references memory corruption vulnerabilities (plural), suggesting multiple fixes may be bundled in the security update. Until patching is complete, organizations should implement defense-in-depth controls: restrict VI file sources to trusted repositories only, implement application whitelisting to prevent unauthorized LabVIEW file execution, and educate users about the risks of opening VI files from untrusted sources or email attachments. Network segmentation can limit lateral movement if exploitation occurs in air-gapped or OT environments where LabVIEW commonly operates. Consider file integrity monitoring for VI files in production environments to detect unauthorized modifications. For legacy systems unable to upgrade immediately, disable unnecessary file format handlers and restrict file system permissions to minimize attack surface.