Skip to main content
CVE-2025-64462VulnerabilityPublished Updated

CVE-2025-64462: NI LabVIEW · Out-of-bounds Read

Affects NI LabVIEWSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
NI LabVIEWAffected
  • =0
  • =23.1.0
  • =24.1.0
  • =25.1.0
Fixed in–

AI-suggested

To mitigate CVE-2025-64462 effectively, organizations should implement a multi-layered approach: 1) Immediately restrict the opening of VI files from untrusted or unknown sources by enforcing strict file handling policies and user training to recognize suspicious files. 2) Employ application whitelisting and sandboxing techniques to isolate LabVIEW processes, limiting the impact of potential exploitation. 3) Monitor and control network shares and email attachments to prevent delivery of malicious VI files. 4) Use endpoint detection and response (EDR) tools to identify anomalous behaviors indicative of exploitation attempts. 5) Regularly back up critical LabVIEW projects and configurations to enable recovery in case of compromise. 6) Stay vigilant for official patches or updates from NI and apply them promptly once available. 7) Consider implementing file integrity monitoring on VI files to detect unauthorized modifications. 8) If feasible, conduct internal code reviews or static analysis on VI files received from external sources to identify potential corruption or malicious constructs. These steps go beyond generic advice by focusing on the unique aspects of LabVIEW’s file handling and operational context.

Description

There is an out of bounds read vulnerability in NI LabVIEW in LVResFile::RGetMemFileHandle() 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.

References

Community reviews

Loading reviews…