CVE-2025-64466: 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
To mitigate CVE-2025-64466, organizations should: 1) Immediately update NI LabVIEW to the latest patched version once available from the vendor, as no patches are currently linked but should be prioritized upon release. 2) Implement strict controls on the sources of VI files, restricting users from opening VI files from untrusted or unknown origins. 3) Employ application whitelisting and sandboxing techniques to limit the execution context of LabVIEW and contain potential exploitation. 4) Educate users about the risks of opening unsolicited or suspicious VI files, incorporating this into security awareness training. 5) Monitor LabVIEW process behavior and system logs for anomalies indicative of exploitation attempts, such as unexpected memory access violations or crashes. 6) Use endpoint detection and response (EDR) tools to detect and block suspicious activities related to LabVIEW. 7) Consider network segmentation to isolate systems running LabVIEW from critical infrastructure to limit lateral movement if compromise occurs. 8) Review and harden file parsing and input validation policies within LabVIEW project workflows to minimize exposure to malformed files.
Description
There is an out of bounds read vulnerability in NI LabVIEW in lvre!ExecPostedProcRecPost() 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.