# CVE-2025-2629: DLL Hijacking Vulnerability in NI LabVIEW When Loading NI Error Reporting

> Attackers can execute arbitrary code by placing a malicious DLL in an uncontrolled search path used by NI LabVIEW for error reporting.

- **Severity:** High 7.0 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Apr 2025
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-922p-pfv2-32j4

## What is CVE-2025-2629?

CVE-2025-2629 is a high-severity vulnerability in NI LabVIEW, published on 9 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2025-2629?

It affects 1 product.


Products: Ni Labview.

## How do I fix CVE-2025-2629?

No fix has been published for CVE-2025-2629 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-2629 being exploited?

There is no known exploitation of CVE-2025-2629 in the wild and no public exploit code.

## Other vulnerabilities in NI LabVIEW

- [CVE-2013-5022](https://insights.sbomify.com/CVE-2013-5022/): Path traversal in n/a (critical 10.0)
- [CVE-2026-16233](https://insights.sbomify.com/CVE-2026-16233/): Out-of-Bounds Write Vulnerability in NI LabVIEW when loading VI (high 8.5)
- [CVE-2026-16234](https://insights.sbomify.com/CVE-2026-16234/): Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI (high 8.5)
- [CVE-2026-64201](https://insights.sbomify.com/CVE-2026-64201/): Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI (high 8.5)
- [CVE-2026-64202](https://insights.sbomify.com/CVE-2026-64202/): Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2629 and fix it if it is affected.

What it is: CVE-2025-2629 is a high-severity vulnerability in NI LabVIEW, published on 9 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-2629 in the wild and no public exploit code.

Affected product: NI LabVIEW. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2629/ (Markdown: https://insights.sbomify.com/CVE-2025-2629/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2629
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2629
- OSV: https://osv.dev/vulnerability/CVE-2025-2629

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2629/
Summaries are generated and may contain mistakes; the official description above is the record.