dbcve.org
LabviewApplication · Ni

CVE-2025-64461

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 write vulnerability in NI LabVIEW in mgocre_SH_25_3!RevBL() 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 write vulnerability exists in NI LabVIEW's mgocre_SH_25_3!RevBL() function when parsing corrupted VI files. The vulnerability allows an attacker to trigger arbitrary memory writes by crafting a malicious VI file, potentially leading to information disclosure or arbitrary code execution upon user opening the file.

MitigationUsers should avoid opening VI files from untrusted sources. Organizations should update to LabVIEW versions beyond 2025 Q3 once the vendor releases a patch, and implement file type validation policies.

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. Confirm LabVIEW installation
    Check system for LabVIEW installation. On Windows, look in Program Files for National Instruments/LabVIEW folders, or check registry under HKLM\SOFTWARE\National Instruments\LabVIEW. On macOS, check /Applications for LabVIEW.app.
    Affected if LabVIEW is installed on the system
  2. Identify installed LabVIEW version
    Open LabVIEW and go to Help > About LabVIEW, or check the version from the installer/registry. The version will be displayed as a year (2022, 2023, 2024, or 2025).
    Affected if The installed version is 2022, 2023, 2024, or 2025
  3. Determine if VI file parsing is accessible
    Verify that users can open VI files through LabVIEW. This is the default behavior when LabVIEW is installed - VI files can be opened via File > Open or by double-clicking a .vi file.
    Affected if LabVIEW can open and parse VI files (default behavior)
  4. Assess user exposure to untrusted VI files
    Check if users routinely open VI files from external sources, network shares, or downloads. Review email attachments, download folders, or shared directories containing .vi files.
    Affected if Users open VI files from untrusted or external sources

A user is affected if LabVIEW version 2022, 2023, 2024, or 2025 is installed and users can open potentially malicious 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

Users should avoid opening VI files from untrusted sources. Organizations should update to LabVIEW versions beyond 2025 Q3 once the vendor releases a patch, and implement file type validation policies.

Recommended fix Moderate confidence

LabVIEW 2025 Q4 or later (any version after 25.3)

  1. 1. Navigate to the National Instruments (NI) website or use the NI Package Manager to check for available LabVIEW updates
  2. 2. Download and install LabVIEW version 2025 Q4 or later (the first release after the affected 2025 Q3 (25.3) version)
  3. 3. Verify the installation by opening LabVIEW and checking the version in Help > About LabVIEW
  4. 4. Ensure all users in your organization who use LabVIEW upgrade to the fixed version
  5. 5. Implement a policy to warn users about opening VI files from untrusted sources, as a defense-in-depth measure
Caveat Review custom VIs and toolkits for compatibility with the new version before deploying widely

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

Fix this in Labview Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing16.0 h
  • Review / QA8.0 h
50.0 hours of engineering $8,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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