Cyber Resilience

CVE-2026-32861

High

Published: 07 April 2026

Published
07 April 2026
Modified
13 April 2026
KEV Added
Patch
CVSS Score v4 8.5 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 Score 0.0022 12.3th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-32861 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Ni Labview. Its CVSS base score is 8.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked at the 12.3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified are NIST 800-53 RA-5 (Vulnerability Monitoring and Scanning) and SI-2 (Flaw Remediation).

Deeper analysis

CVE-2026-32861 is a memory corruption vulnerability stemming from an out-of-bounds write that occurs when NI LabVIEW loads a corrupted LVCLASS file. This flaw affects NI LabVIEW 2026 Q1 (version 26.1.0) and all prior versions. Classified under CWE-787, it carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), indicating high impact on confidentiality, integrity, and availability.

Exploitation requires an attacker to entice a user into opening a specially crafted .lvclass file within a vulnerable LabVIEW installation. As a local attack vector with no required privileges but necessitating user interaction, a successful exploit could lead to information disclosure or arbitrary code execution on the affected system.

The official NI security advisory details available critical and security updates to address this LV class file parsing memory corruption vulnerability in LabVIEW, available at https://www.ni.com/en/support/security/available-critical-and-security-updates-for-ni-software/2026/lv-class-file-parsing-memory-corruption-vulnerability-in-ni-labview.html. Security practitioners should apply these patches promptly to vulnerable installations.

EU & UK References

Vulnerability details

There is a memory corruption vulnerability due to an out-of-bounds write when loading a corrupted LVCLASS file in NI LabVIEW. This vulnerability may result in information disclosure or arbitrary code execution. Successful exploitation requires an attacker to get a user…

more

to open a specially crafted .lvclass file. This vulnerability affects NI LabVIEW 2026 Q1 (26.1.0) and prior versions.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1204.002 Malicious File Execution
An adversary may rely upon a user opening a malicious file in order to gain execution.
Why these techniques?

Memory corruption in LVCLASS file parser enables client-side RCE when user opens malicious file (T1203 Exploitation for Client Execution + T1204.002 Malicious File).

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-32860Same product: Ni Labview
CVE-2026-32862Same product: Ni Labview
CVE-2026-32864Same product: Ni Labview
CVE-2026-32863Same product: Ni Labview
CVE-2026-0957Same vendor: Ni
CVE-2026-0954Same vendor: Ni
CVE-2026-0955Same vendor: Ni
CVE-2025-2449Same vendor: Ni
CVE-2025-27169Shared CWE-787
CVE-2026-0874Shared CWE-787

Affected Assets

ni
labview
2023, 2024, 2025, 2026 · ≤ 2022

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires timely identification, reporting, and correction of the memory corruption flaw in NI LabVIEW via vendor patches to prevent exploitation.

preventdetect

Mandates vulnerability scanning to identify systems with vulnerable LabVIEW versions and remediation within defined timeframes, addressing this specific CVE.

prevent

Provides memory protection mechanisms like ASLR and DEP to mitigate the impact of out-of-bounds writes during LVCLASS file parsing, hindering arbitrary code execution.

References