dbcve.org
LabviewApplication · Ni

CVE-2025-64466

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!ExecPostedProcRecPost() 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 · moderate confidence

An out-of-bounds read vulnerability exists in NI LabVIEW's lvre!ExecPostedProcRecPost() function when parsing corrupted VI files. This allows an attacker to read memory beyond allocated buffers by tricking a user into opening a specially crafted VI file, potentially leading to information disclosure or arbitrary code execution.

MitigationOnly open VI files from trusted sources and await an official patch from NI. Consider implementing file validation policies and user training on the risks of opening untrusted files until a fixed version is available.

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. Verify NI LabVIEW is installed
    Check for LabVIEW installation directories (typically C:\Program Files\National Instruments\LabVIEW XXXX) or use Windows Add/Remove Programs to list installed software
    Affected if NI LabVIEW software is present on the system
  2. Identify installed LabVIEW version
    Open LabVIEW and go to Help > About LabVIEW, or check the installation directory name (e.g., LabVIEW 2022, LabVIEW 2023, LabVIEW 2024, LabVIEW 2025)
    Affected if The installed version corresponds to year-based releases 2022, 2023, 2024, or 2025
  3. Confirm version falls within affected range
    Match your installed LabVIEW year version (e.g., 2022, 2023, 2024, or 2025) against the affected list - all versions within these four year releases are considered affected
    Affected if The installed LabVIEW version is any release within 2022, 2023, 2024, or 2025 years
  4. Assess risk from untrusted VI files
    Determine whether the LabVIEW environment is used to open VI files from external or untrusted sources, or if file validation policies exist
    Affected if Users routinely open VI files from untrusted or unknown sources without validation

You are affected if NI LabVIEW versions 2022, 2023, 2024, or 2025 are installed AND users open untrusted or specially crafted VI files with the software.

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

Only open VI files from trusted sources and await an official patch from NI. Consider implementing file validation policies and user training on the risks of opening untrusted files until a fixed version is available.

Recommended fix Moderate confidence

LabVIEW version newer than 2025 Q3 (25.3) - contact NI for exact version number

  1. 1. Navigate to the official NI (National Instruments) website at www.ni.com to obtain the latest LabVIEW version.
  2. 2. Download and install the most recent LabVIEW version newer than 2025 Q3 (25.3).
  3. 3. Before deploying, test critical VI files in the new environment to ensure compatibility.
  4. 4. Distribute updated LabVIEW to all users and remind them not to open VI files from untrusted sources.
Caveat Newer LabVIEW versions may introduce breaking changes in VI file formats or function behavior; test thoroughly before production deployment

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

Fix this in Labview Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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