dbcve.org
LabviewApplication · Ni

CVE-2025-64465

HIGH · 7.8 CVSS v3.1 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
There is an out of bounds read vulnerability in NI LabVIEW in lvre!DataSizeTDR() 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An out-of-bounds read vulnerability exists in NI LabVIEW's lvre!DataSizeTDR() function when parsing corrupted VI files. The vulnerability occurs due to insufficient bounds checking during file parsing, potentially allowing an attacker to read arbitrary memory contents or achieve code execution by tricking a user into opening a specially crafted malicious VI file.

MitigationUsers should refrain from opening VI files from untrusted or unknown sources. Organizations should implement file screening and sandboxing for received VI files until an official patch is available from National Instruments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LabviewApplication
Affected:= 2022= 2023= 2024= 2025

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify LabVIEW installation and version
    Check the Windows registry at HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LabVIEW for the "Default Version" value, or inspect the LabVIEW installation directory (typically C:\Program Files\National Instruments\LabVIEW XX) for version folders.
    Affected if Installed version matches 2022, 2023, 2024, or 2025
  2. Locate the lvre library
    Navigate to the LabVIEW installation directory and locate lvre.dll or lvrt.dll (the LabVIEW Run-Time library), typically found in the \lib\msvc or \resource\plugins subdirectory.
    Affected if The lvre runtime library exists in the LabVIEW installation directory for versions 2022-2025
  3. Verify VI file handling capability
    Confirm that LabVIEW can open and parse VI files by checking file association settings in Windows (HKEY_CLASSES_ROOT\.vi) or by attempting to view a VI file's internal structure using a hex editor.
    Affected if LabVIEW is configured to open .vi files, enabling parsing of the vulnerable lvre!DataSizeTDR() function
  4. Check for untrusted VI file reception
    Inspect user-accessible directories (Downloads, email attachments, network shares) for .vi files, or review email gateway/web proxy logs for incoming VI file transfers.
    Affected if Users have received or can receive VI files from untrusted or unknown sources that could trigger the vulnerable parsing code

Environment is affected if NI LabVIEW versions 2022 through 2025 are installed and users can open VI files from untrusted sources, enabling the out-of-bounds read in the lvre!DataSizeTDR() function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Users should refrain from opening VI files from untrusted or unknown sources. Organizations should implement file screening and sandboxing for received VI files until an official patch is available from National Instruments.

Recommended fix Moderate confidence

NI LabVIEW 2025 Q4 (25.4) or later

  1. 1. Identify the currently installed NI LabVIEW version by opening LabVIEW and navigating to Help > About LabVIEW, or by checking Add/Remove Programs in Windows
  2. 2. Obtain the fixed version of NI LabVIEW from the official NI website (www.ni.com) or the NI Installer
  3. 3. Download NI LabVIEW 2025 Q4 (25.4) or later from the official NI download page
  4. 4. Before upgrading, back up any custom VIs, libraries, and projects
  5. 5. Run the NI Installer and follow the on-screen instructions to upgrade LabVIEW
  6. 6. Verify the installation completed successfully by opening LabVIEW and confirming the version in Help > About LabVIEW
  7. 7. Test that previously affected VI files no longer trigger the vulnerability
Caveat Upgrading LabVIEW may require recompiling VIs; verify compatibility with any third-party modules or toolkits; ensure system meets hardware and software requirements for the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Labview Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64465 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64465 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data