Code execution via out-of-bounds VI parsing
Published Dec 18, 2025 · Updated Dec 18, 2025
Out-of-bounds read in lvre!DataSizeTDR() in NI LabVIEW 2025 Q3 and earlier allows attackers to disclose data or execute code via a crafted VI. The lvre!DataSizeTDR() routine reads beyond the valid buffer boundary while parsing corrupted VI data. Exploitation requires a user to open the specially crafted VI, and the resulting memory corruption runs within the user's LabVIEW process and privileges.
Summary
What happened
Out-of-bounds read in lvre!DataSizeTDR() in NI LabVIEW 2025 Q3 and earlier allows attackers to disclose data or execute code via a crafted VI. The lvre!DataSizeTDR() routine reads beyond the valid buffer boundary while parsing corrupted VI data. Exploitation requires a user to open the specially crafted VI, and the resulting memory corruption runs within the user's LabVIEW process and privileges.
The record
- CVE
- CVE-2025-64465
- Published
- Dec 18, 2025
- Updated
- Dec 18, 2025
- Vendor
- National Instruments
- Product
- LabVIEW
- Classifications
- CWE-125, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 18, 2025CVE publishedPublication date reported by the CVE source.
- Dec 18, 2025Record 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 <=22.3.6
- Affected versionversion=23.1.0 <=23.3.7
- Affected versionversion=24.1.0 <=24.3.4
- Affected versionversion=25.1.0 <=25.3.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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