Arbitrary code execution via LVCLASS out-of-bounds write
Published Apr 7, 2026 · Updated Apr 7, 2026
Out-of-bounds write in NI LabVIEW 2026 Q1 and earlier allows context-dependent attackers to execute arbitrary code via an LVCLASS file. The LVCLASS file parser fails to validate user-supplied class data before writing it to memory, corrupting process memory outside the intended bounds. Exploitation requires a user to open a specially crafted .lvclass file, after which code runs in the context of the LabVIEW process or process memory is disclosed.
Summary
What happened
Out-of-bounds write in NI LabVIEW 2026 Q1 and earlier allows context-dependent attackers to execute arbitrary code via an LVCLASS file. The LVCLASS file parser fails to validate user-supplied class data before writing it to memory, corrupting process memory outside the intended bounds. Exploitation requires a user to open a specially crafted .lvclass file, after which code runs in the context of the LabVIEW process or process memory is disclosed.
The record
- CVE
- CVE-2026-32861
- Published
- Apr 7, 2026
- Updated
- Apr 7, 2026
- Vendor
- National Instruments
- Product
- LabVIEW
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2026CVE publishedPublication date reported by the CVE source.
- Apr 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <23.0.0
- Affected versionversion=23.1.0 <23.3.9
- Affected versionversion=24.1.0 <24.3.6
- Affected versionversion=25.1.0 <25.3.4
- Affected versionversion=26.1.0 <26.1.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo