NI LabVIEW up to 22.x/23.3.8/24.3.5/25.3.3/26.1.0 LVLIB File Parser out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.99- |
Summary
A vulnerability has been found in NI LabVIEW up to 22.x/23.3.8/24.3.5/25.3.3/26.1.0 and classified as critical. This impacts an unknown function of the component LVLIB File Parser. The manipulation leads to out-of-bounds write. This vulnerability is referenced as CVE-2026-32860. Remote exploitation of the attack is possible. No exploit is available. The affected component should be upgraded.
Details
A vulnerability, which was classified as critical, has been found in NI LabVIEW up to 22.x/23.3.8/24.3.5/25.3.3/26.1.0. This issue affects an unknown part of the component LVLIB File Parser. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. Using CWE to declare the problem leads to CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
There is a memory corruption vulnerability due to an out-of-bounds write when loading a corrupted LVLIB file 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 .lvlib file. This vulnerability affects NI LabVIEW 2026 Q1 (26.1.0) and prior versions.
The weakness was published by Rocco Calvi. The advisory is shared at ni.com. The identification of this vulnerability is CVE-2026-32860 since 03/16/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 23.0.0, 23.3.9, 24.3.6, 25.3.4 or 26.1.1 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 22.x
- 23.3.0
- 23.3.1
- 23.3.2
- 23.3.3
- 23.3.4
- 23.3.5
- 23.3.6
- 23.3.7
- 23.3.8
- 24.3.0
- 24.3.1
- 24.3.2
- 24.3.3
- 24.3.4
- 24.3.5
- 25.3.0
- 25.3.1
- 25.3.2
- 25.3.3
- 26.0
- 26.1.0
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.0VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Out-of-bounds writeCWE: CWE-787 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: LabVIEW 23.0.0/23.3.9/24.3.6/25.3.4/26.1.1
Timeline
03/16/2026 CVE reserved04/07/2026 Advisory disclosed
04/07/2026 VulDB entry created
04/07/2026 VulDB entry last update
Sources
Advisory: ni.comResearcher: Rocco Calvi
Status: Confirmed
CVE: CVE-2026-32860 (🔒)
GCVE (CVE): GCVE-0-2026-32860
GCVE (VulDB): GCVE-100-355925
Entry
Created: 04/07/2026 23:26Changes: 04/07/2026 23:26 (76)
Complete: 🔍
Cache ID: 216:250:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.