Code execution via LVGetFileType out-of-bounds read
Published Aug 25, 2026 · Updated Aug 26, 2026
Out-of-bounds read in NI LabVIEW 26.3.0 and earlier allows attackers to disclose memory or execute code through a crafted VI. The LVGetFileType function reads beyond a buffer while loading malformed VI file data. Exploitation requires user interaction to open the file, after which attacker-controlled code can run in the LabVIEW process context.
Summary
What happened
Out-of-bounds read in NI LabVIEW 26.3.0 and earlier allows attackers to disclose memory or execute code through a crafted VI. The LVGetFileType function reads beyond a buffer while loading malformed VI file data. Exploitation requires user interaction to open the file, after which attacker-controlled code can run in the LabVIEW process context.
The record
- CVE
- CVE-2026-64202
- Published
- Aug 25, 2026
- Updated
- Aug 26, 2026
- Vendor
- National Instruments
- Product
- LabVIEW
- Classifications
- CWE-125, CAPEC-100, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 26, 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.10
- Affected versionversion=24.1.0 <24.3.7
- Affected versionversion=25.1.0 <25.3.5
- Affected versionversion=26.1.0 <26.3.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