dbcve.org
LabviewApplication · Ni

CVE-2025-7361

HIGH · 7.8 CVSS v3.1 Published 2025-07-29
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
A code injection vulnerability due to an improper initialization check exists in NI LabVIEW that may result in arbitrary code execution. Successful exploitation requires an attacker to get a user to open a specially crafted VI using a CIN node. This vulnerability affects 32-bit NI LabVIEW 2025 Q1 and prior versions. LabVIEW 64-bit versions do not support CIN nodes and are not affected.

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

A code injection vulnerability exists in 32-bit NI LabVIEW versions 2025 Q1 and prior due to an improper initialization check in the CIN (Code Interface Node) functionality. An attacker can craft a malicious VI file that, when opened by a user, allows arbitrary code execution through the CIN node. The vulnerability does not affect 64-bit LabVIEW versions as they do not support CIN nodes.

MitigationUpdate to a patched version of LabVIEW when released by NI, and exercise caution when opening VI files from untrusted sources. Consider migrating to 64-bit LabVIEW if CIN node functionality is not required, as this variant is not affected.

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 LabVIEW installation architecture
    Check if the installed LabVIEW is 32-bit or 64-bit. Look for 'LabVIEW 32-bit' or 'LabVIEW (32-bit)' in the Start Menu, or check the program files directory (Program Files (x86)\National Instruments\ for 32-bit vs Program Files\National Instruments\ for 64-bit).
    Affected if The installation is 32-bit LabVIEW. The vulnerability does NOT affect 64-bit LabVIEW as CIN nodes are not supported.
  2. Determine LabVIEW version number
    Open LabVIEW and go to Help > About LabVIEW, or check the version in the installation directory or NI MAX software. Compare the version year (2022, 2023, 2024, 2025) and any Q1 designation against the affected range.
    Affected if The installed version is 2025 Q1 or prior, or any version listed as 2021, 2022, 2023, 2024, or 2025.
  3. Locate CIN nodes in projects
    Search project files (.lvproj) and VI files (.vi) for 'CIN' or 'Code Interface Node' references. In LabVIEW, open the Functions palette and check if CIN nodes are available under the Connectivity or Hardware Input/Output categories.
    Affected if CIN nodes exist in any project or the CIN palette is accessible in the 32-bit LabVIEW environment.
  4. Inspect VI files from external sources
    If VI files from untrusted sources are present, examine them using the LabVIEW VI Analyzer or by reviewing the block diagram for CIN nodes that may execute external code.
    Affected if A VI file contains a CIN node configured to call external code, which could be exploited by a maliciously crafted VI.

A user is affected if they have 32-bit LabVIEW version 2025 Q1 or earlier installed AND have access to or use CIN nodes in their LabVIEW environment.

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

Update to a patched version of LabVIEW when released by NI, and exercise caution when opening VI files from untrusted sources. Consider migrating to 64-bit LabVIEW if CIN node functionality is not required, as this variant is not affected.

Recommended fix Moderate confidence

NI LabVIEW 64-bit (any current version) or LabVIEW 2025 Q3+ (32-bit)

  1. 1. Identify whether you are running 32-bit or 64-bit LabVIEW by opening LabVIEW and checking Help > About LabVIEW
  2. 2. If running 32-bit LabVIEW, consider migrating to 64-bit LabVIEW which does not support CIN nodes and is not affected by this vulnerability
  3. 3. If 64-bit migration is not feasible, upgrade to the latest 32-bit LabVIEW version available from NI (currently LabVIEW 2025 Q3 or later)
  4. 4. After upgrading, verify all existing VIs function correctly, particularly any that previously used CIN nodes
  5. 5. Implement user training to never open VIs from untrusted sources, as exploitation requires user interaction to open a specially crafted VI
Caveat Migrating to 64-bit LabVIEW may require recompilation of external code interfaces and may have memory address implications for existing applications

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

Fix this in Labview Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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