dbcve.org
LabviewApplication · Ni

CVE-2025-2629

HIGH · 7.8 CVSS v3.1 Published 2025-04-09
Fix available
A fix is available. Upgrade to after 2021 or later.
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 DLL hijacking vulnerability due to an uncontrolled search path that exists in NI LabVIEW when loading NI Error Reporting. This vulnerability may result in arbitrary code execution. Successful exploitation requires an attacker to insert a malicious DLL into the uncontrolled search path. This vulnerability affects NI LabVIEW 2025 Q1 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

This is a DLL hijacking vulnerability in NI LabVIEW caused by an uncontrolled search path when loading the NI Error Reporting component. An attacker can place a malicious DLL in the search path to achieve arbitrary code execution with the privileges of the LabVIEW process.

MitigationReplace uncontrolled DLL search path usage with secure DLL loading practices such as absolute paths, safe DLL search mode enabled, or DLL redirection; also ensure writable directories are not in the DLL search path.

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:<= 2021= 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 if NI LabVIEW is installed
    Check for LabVIEW installation directory. Common paths: C:\Program Files\National Instruments\LabVIEW [version] or C:\Program Files (x86)\National Instruments\LabVIEW [version]. Also check Programs and Features for 'National Instruments LabVIEW'.
    Affected if LabVIEW is installed and version is 2021 or earlier, or 2022, 2023, 2024, or 2025.
  2. Confirm LabVIEW version
    Run 'labview --version' from command line in LabVIEW bin directory, or check the version listed in Programs and Features, or open LabVIEW and check Help > About LabVIEW.
    Affected if Installed version matches <= 2021, 2022, 2023, 2024, or 2025.
  3. Locate NI Error Reporting component
    Search for 'nierr.dll' or 'NI Error Reporting' in the LabVIEW installation directory, typically under C:\Program Files\National Instruments\LabVIEW[version]\resource\ or C:\Program Files\National Instruments\Shared\Error Reporting\.
    Affected if The NI Error Reporting DLL (nierr.dll) exists in the LabVIEW installation.
  4. Examine DLL search path configuration
    Open Windows Environment Variables editor (System Properties > Environment Variables) and check the PATH variable. Also check if LabVIEW adds directories to PATH. Use 'echo %PATH%' in command prompt after launching LabVIEW to see the full search path.
    Affected if Writable directories (user home, temp, downloads) appear in the PATH before the LabVIEW installation directory.
  5. Check for suspicious DLLs in LabVIEW directories
    Use File Explorer to list all DLL files in LabVIEW\bin and LabVIEW\resource\ directories. Look for unexpected or recently modified DLLs, especially with names similar to system DLLs (e.g., version.dll, ntdll.dll, kernel32.dll) placed in LabVIEW directories.
    Affected if Unexpected DLL files exist in LabVIEW directories, particularly in locations that would be loaded before the legitimate NI Error Reporting component.

You are affected if NI LabVIEW version 2021 or earlier, 2022, 2023, 2024, or 2025 is installed and the NI Error Reporting component is present with an uncontrolled DLL search path that includes writable directories.

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
Upgrade available Upgrade to a release after 2021
Interim mitigation

Replace uncontrolled DLL search path usage with secure DLL loading practices such as absolute paths, safe DLL search mode enabled, or DLL redirection; also ensure writable directories are not in the DLL search path.

Recommended fix Moderate confidence

LabVIEW version with security fix (contact NI for specific version number - likely 2025 Q2 or later)

  1. Check NI's official support website (www.ni.com) or contact NI technical support for the specific patch version that addresses CVE-2025-2629
  2. Verify your current LabVIEW version by opening LabVIEW and going to Help > About LabVIEW
  3. If a patch is available from NI, download and apply it following NI's official installation instructions
  4. If no patch is available, ensure the LabVIEW working directory and directories in the PATH environment variable are secured against write access by non-administrative users
  5. Do not place any untrusted DLLs in directories that LabVIEW uses or accesses
  6. Restrict write permissions on LabVIEW installation directories to administrators only
Caveat Check NI's release notes for any breaking changes in the security update before applying to production environments

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

Fix this in Labview Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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