CVE-2025-64464: NI LabVIEW · Out-of-bounds Read
Affects NI LabVIEWSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| NI LabVIEW | Affected
| Fixed in– |
AI-suggested
Organizations should immediately review their use of NI LabVIEW and restrict the opening of VI files from untrusted or unknown sources. Implement strict access controls and user training to reduce the risk of social engineering attacks that could lead to exploitation. Employ application whitelisting and sandboxing techniques to limit the execution context of LabVIEW and isolate it from critical systems. Monitor for unusual activity related to LabVIEW processes and file access patterns. Since no official patches are listed yet, coordinate with NI for timely updates or security advisories. Consider deploying endpoint detection and response (EDR) solutions capable of detecting anomalous memory access or code execution behaviors. Regularly back up critical LabVIEW projects and system configurations to enable recovery in case of compromise. Finally, implement network segmentation to limit the spread of any potential compromise originating from affected LabVIEW hosts.
Description
There is an out of bounds read vulnerability in NI LabVIEW in lvre!VisaWriteFromFile() when parsing a corrupted VI file. 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 VI. This vulnerability affects NI LabVIEW 2025 Q3 (25.3) and prior versions.