Code execution via VI-file integer overflow
Published Aug 25, 2026 · Updated Aug 27, 2026
Integer overflow in NI LabVIEW 2026 Q3 and earlier allows attackers to execute arbitrary code by convincing a user to open a crafted VI file. During VI-file loading, an integer calculation overflows and the resulting value drives a write beyond the intended buffer; NI has not identified the affected routine. Exploitation requires user interaction with a crafted local file and can disclose data or execute code in the LabVIEW process.
Summary
What happened
Integer overflow in NI LabVIEW 2026 Q3 and earlier allows attackers to execute arbitrary code by convincing a user to open a crafted VI file. During VI-file loading, an integer calculation overflows and the resulting value drives a write beyond the intended buffer; NI has not identified the affected routine. Exploitation requires user interaction with a crafted local file and can disclose data or execute code in the LabVIEW process.
The record
- CVE
- CVE-2026-18445
- Published
- Aug 25, 2026
- Updated
- Aug 27, 2026
- Vendor
- National Instruments
- Product
- LabVIEW
- Classifications
- CWE-190, CAPEC-100, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 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