CVE-2025-64463: 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 implement strict controls on the handling and opening of VI files, especially those received from untrusted or external sources. Employ application whitelisting and sandboxing techniques to isolate LabVIEW processes and limit the impact of potential exploitation. Network segmentation can reduce exposure of critical systems running LabVIEW. Until official patches are released, consider disabling or restricting the use of LabVIEW on endpoints that are exposed to untrusted file sources. Educate users about the risks of opening unsolicited VI files and enforce policies for verifying file integrity and provenance. Monitor systems for unusual behavior indicative of exploitation attempts, such as unexpected memory access patterns or process anomalies. Engage with NI support channels to obtain updates on patch availability and apply them promptly once released. Additionally, maintain up-to-date backups of critical VI files and system configurations to enable recovery in case of compromise.
Description
There is an out of bounds read vulnerability in NI LabVIEW in LVResource::DetachResource() 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.