NI LabVIEW is vulnerable to a memory corruption flaw caused by an out-of-bounds write when opening a specially crafted .lvlib file. The vulnerability can lead to information disclosure or, more critically, arbitrary code execution if the malicious file is opened by an affected user. This type of flaw permits an attacker to overwrite arbitrary memory locations, potentially allowing execution of attacker‑supplied code within the LabVIEW process.

All NI LabVIEW installations up to and including 2026 Q1 (version 26.1.0) are affected. This includes earlier 2026 releases as well as all 2026 Q1 patches prior to the final fix. The vulnerability exists in the library file parsing component of LabVIEW and is present in any version that traditionally receives a Q1 update cycle.

The CVSS score of 8.5 indicates high severity, while the EPSS score of less than 1% suggests low probability of exploitation in the wild. The vulnerability is not yet listed in the CISA KEV catalog. Exploitation requires the user to open a malicious .lvlib file, implying a typical user‑interfacial or removable‑media vector. The necessity of a user action reduces the likelihood of automated attacks but still poses a significant risk when documents are shared through social engineering or compromised storage media.