dbcve.org
LabviewApplication · Ni

CVE-2025-64463

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 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.

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 LVResource::DetachResource() function when parsing corrupted VI files. This memory safety issue in file parsing code can lead to information disclosure or potentially arbitrary code execution when a user opens a specially crafted malicious VI file.

MitigationUntil an official patch is released by NI, organizations should implement controls preventing users from opening VI files from untrusted sources, and consider file scanning or sandboxing for LabVIEW files.

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. Check if NI LabVIEW is installed
    Look for LabVIEW installation directory, typically in C:\Program Files\National Instruments\ or C:\Program Files (x86)\National Instruments\, or check Windows Registry under HKLM\SOFTWARE\National Instruments\LabVIEW
    Affected if LabVIEW is found on the system
  2. Determine the installed LabVIEW version
    Check the version folder name in the installation directory (e.g., LabVIEW 2022, LabVIEW 2023, LabVIEW 2024, LabVIEW 2025) or query the Windows Registry key HKLM\SOFTWARE\National Instruments\LabVIEW\Version
    Affected if The version matches 2022, 2023, 2024, or 2025
  3. Verify the specific minor version if applicable
    Check LabVIEW Help > About LabVIEW within the application, or examine the file version of LabVIEW.exe in the bin directory
    Affected if The installed version is any release within the 2022-2025 annual versions

A user is affected if NI LabVIEW version 2022, 2023, 2024, or 2025 is installed and they open a specially crafted malicious VI file from an untrusted source.

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

Until an official patch is released by NI, organizations should implement controls preventing users from opening VI files from untrusted sources, and consider file scanning or sandboxing for LabVIEW files.

Recommended fix High confidence

LabVIEW version later than 2025 Q3 (25.3) - contact NI for the specific fixed release number

  1. 1. Obtain the latest version of NI LabVIEW from the official National Instruments (NI) website or through your NI software subscription.
  2. 2. Verify that the new version is later than 25.3 (2025 Q3) to ensure the vulnerability is patched.
  3. 3. Download the installer for the fixed LabVIEW version.
  4. 4. Before installing, back up any critical VI files and projects.
  5. 5. Uninstall the current affected LabVIEW version if necessary, or perform an in-place upgrade.
  6. 6. Install the new LabVIEW version following NI's installation instructions.
  7. 7. After installation, verify the version number matches the expected fixed release.
  8. 8. Test that existing VI files open correctly in the new version.
Caveat Review NI's release notes for your specific version transition for any API changes or migration requirements

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

Fix this in Labview Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64463 — 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-64463 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