NI LabVIEW Out-of-Bounds Read Vulnerability (CVE-2026-32864)
A memory corruption vulnerability exists in NI LabVIEW due to an out-of-bounds read in mgcore_SH_25_3!aligned_free(), potentially leading to information disclosure or arbitrary code execution if a user opens a specially crafted VI file.
A memory corruption vulnerability, identified as CVE-2026-32864, exists within National Instruments (NI) LabVIEW software. The flaw is triggered by an out-of-bounds read within the mgcore_SH_25_3!aligned_free() function. An attacker can exploit this vulnerability by enticing a user to open a specially crafted VI (Virtual Instrument) file. Successful exploitation could lead to information disclosure, potentially exposing sensitive data handled by LabVIEW, or arbitrary code execution, granting the attacker control over the affected system. This vulnerability affects NI LabVIEW versions 2026 Q1 (26.1.0) and all prior versions, making a wide range of LabVIEW installations susceptible.
Attack Chain
- An attacker crafts a malicious LabVIEW VI file designed to trigger the out-of-bounds read in
mgcore_SH_25_3!aligned_free(). - The attacker uses social engineering to convince a victim to open the specially crafted VI file.
- The victim opens the malicious VI file using a vulnerable version of NI LabVIEW (2026 Q1 (26.1.0) and prior).
- LabVIEW attempts to process the malformed data within the VI file.
- The
mgcore_SH_25_3!aligned_free()function is called during the VI file processing. - The out-of-bounds read occurs when
aligned_free()attempts to access memory outside of allocated bounds. - Depending on the memory layout, this can lead to information disclosure by leaking memory contents, or arbitrary code execution by overwriting critical data.
- If arbitrary code execution is achieved, the attacker can then install malware, exfiltrate data, or perform other malicious actions on the compromised system.
Impact
Successful exploitation of CVE-2026-32864 can have serious consequences. Information disclosure could expose sensitive data processed by LabVIEW, such as measurement data, control algorithms, or proprietary code. Arbitrary code execution would allow an attacker to gain complete control over the affected system, enabling them to install malware, steal data, or disrupt operations. The vulnerability affects a broad range of LabVIEW users, potentially impacting industrial control systems, research and development environments, and other critical applications.
Recommendation
- Apply the patch provided by National Instruments for CVE-2026-32864 to remediate the out-of-bounds read vulnerability. Refer to the NI security advisory for specific instructions.
- Deploy the Sigma rule
LabVIEW_Suspicious_VI_File_Opento detect suspicious LabVIEW VI files being opened based on file path or other attributes. - Monitor process creation events for
LabVIEW.exespawning unusual child processes or accessing unusual network resources after a VI file has been opened, which could indicate successful code execution (seeLabVIEW_Suspicious_Child_Processrule). - Educate users about the risks of opening untrusted VI files and emphasize the importance of verifying the source of any VI file before opening it.
Detection coverage 2
LabVIEW Suspicious VI File Open
mediumDetects the opening of LabVIEW VI files from unusual locations, potentially indicating a malicious file.
LabVIEW Suspicious Child Process
highDetects LabVIEW spawning unusual child processes, indicating potential code execution from a malicious VI file.
Detection queries are kept inside the platform. Get full rules →
Indicators of compromise
1
| Type | Value |
|---|---|
| [email protected] |