CVE-2026-32860
Out-of-Bounds Write in NI LabVIEW LVLIB Causes Code Execution
Publication date: 2026-04-07
Last updated on: 2026-04-13
Assigner: National Instruments
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ni | labview | 2024 |
| ni | labview | 2023 |
| ni | labview | 2023 |
| ni | labview | 2023 |
| ni | labview | 2023 |
| ni | labview | 2023 |
| ni | labview | 2023 |
| ni | labview | 2024 |
| ni | labview | 2024 |
| ni | labview | 2024 |
| ni | labview | 2023 |
| ni | labview | 2024 |
| ni | labview | 2025 |
| ni | labview | 2025 |
| ni | labview | 2023 |
| ni | labview | 2024 |
| ni | labview | 2025 |
| ni | labview | 2023 |
| ni | labview | 2024 |
| ni | labview | 2024 |
| ni | labview | 2025 |
| ni | labview | 2025 |
| ni | labview | 2025 |
| ni | labview | 2025 |
| ni | labview | to 2022 (inc) |
| ni | labview | 2023 |
| ni | labview | 2024 |
| ni | labview | 2025 |
| ni | labview | 2026 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-32860 is a memory corruption vulnerability in NI LabVIEW caused by an out-of-bounds write when loading a corrupted project library (.lvlib) file.
This flaw occurs if a user opens a specially crafted .lvlib file, which can lead to information disclosure or arbitrary code execution.
It affects NI LabVIEW 2026 Q1 and all prior versions.
How can this vulnerability impact me? :
If exploited, this vulnerability can result in an attacker gaining access to sensitive information (information disclosure) or executing arbitrary code on the affected system.
Successful exploitation requires a user to open a specially crafted .lvlib file, which means user interaction is necessary.
The impact severity is high, with potential consequences including compromise of confidentiality, integrity, and availability of the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability occurs when a user opens a specially crafted .lvlib file in NI LabVIEW. Detection involves monitoring for the presence or opening of suspicious or unexpected .lvlib files on your system.
Since the vulnerability requires user interaction to open a malicious file, network detection might focus on identifying the transfer or download of .lvlib files from untrusted sources.
There are no specific commands provided in the available resources to detect exploitation or presence of this vulnerability.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade NI LabVIEW to a patched version that addresses this vulnerability.
- Upgrade to LabVIEW 2026 Q1 Patch 1 or later.
- Alternatively, upgrade to LabVIEW 2025 Q3 Patch 4 or later.
- Alternatively, upgrade to LabVIEW 2024 Q3 Patch 6 or later.
- Alternatively, upgrade to LabVIEW 2023 Q3 Patch 9 or later.
Avoid opening .lvlib files from untrusted or unknown sources to reduce the risk of exploitation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how this vulnerability directly affects compliance with common standards and regulations such as GDPR or HIPAA.