dbcve.org
LabviewApplication · Ni

CVE-2025-64469

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 a stack-based buffer overflow vulnerability in NI LabVIEW in LVResFile::FindRsrcListEntry() 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

Stack-based buffer overflow in LVResFile::FindRsrcListEntry() when LabVIEW parses corrupted VI files. The vulnerability allows information disclosure or arbitrary code execution if a user opens a specially crafted malicious VI file.

MitigationDo not open VI files from untrusted sources. Update LabVIEW to a version beyond 2025 Q3 (25.3) when a patch becomes 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. Check if LabVIEW is installed
    Look for LabVIEW installation directories such as C:\Program Files\National Instruments\LabVIEW 20XX or /Applications/National Instruments/LabVIEW 20XX on macOS. On Linux, check /usr/local/ni/labview20XX or /opt/ni/labview20XX.
    Affected if LabVIEW is found in standard installation directories
  2. Identify the installed LabVIEW version
    Open LabVIEW and go to Help > About LabVIEW, or check the version in the installation directory name. On Windows, you may also check the file properties of the LabVIEW executable (LabVIEW.exe) in the installation folder.
    Affected if The installed version is 2022, 2023, 2024, or 2025 (any point release within these years)
  3. Confirm the vulnerability trigger condition
    The flaw only activates when LabVIEW opens a specially crafted malicious VI file. Check if the system or user workflow involves opening VI files, particularly from external or untrusted sources.
    Affected if LabVIEW 2022-2025 is installed AND VI files are opened on the system

You are affected if LabVIEW versions 2022 through 2025 are installed and you open VI files, since the buffer overflow triggers during parsing of corrupted VI files.

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

Do not open VI files from untrusted sources. Update LabVIEW to a version beyond 2025 Q3 (25.3) when a patch becomes available.

Recommended fix High confidence

LabVIEW 2025 Q4 (25.4) or later

  1. 1. Verify current LabVIEW version by opening LabVIEW and navigating to Help > About NI LabVIEW
  2. 2. Download LabVIEW 2025 Q4 (25.4) or later from www.ni.com or the NI License Manager
  3. 3. Back up all existing VI files and LabVIEW projects before upgrading
  4. 4. Run the installer for LabVIEW 2025 Q4 (25.4) or later
  5. 5. Restart the system after installation completes
  6. 6. Verify the upgrade by checking Help > About NI LabVIEW shows version 25.4 or higher
  7. 7. Test critical VI files to ensure functionality is preserved
Caveat Minor: Verify that any VI files created in newer versions still work with your project's supported LabVIEW version; some features may require re-saving VIs in 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
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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