Skip to main content
VulnerabilityPublished

CVE-2025-2633: NI LabVIEW · Improper Validation of Specified Index, Position, or Offset in Input

Affects NI LabVIEWSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
NI LabVIEWAffected
  • 0 – 25.0.0
4 affected builds
Fixed in–

AI-suggested

  1. Immediate mitigation should include user awareness training to avoid opening untrusted or unexpected VI files, emphasizing the risk of social engineering attacks.
  2. Implement strict access controls and network segmentation to limit LabVIEW environment exposure, especially restricting local access to trusted users and systems.
  3. Monitor and audit LabVIEW file usage and execution logs to detect anomalous activity indicative of exploitation attempts.
  4. Employ endpoint protection solutions capable of detecting suspicious behavior related to LabVIEW processes.
  5. Coordinate with NI for timely patch deployment once available; in the interim, consider disabling or restricting the use of vulnerable LabVIEW components where feasible.
  6. Use application whitelisting to prevent execution of unauthorized VI files.
  7. For critical environments, consider sandboxing LabVIEW usage or running it in isolated virtual machines to contain potential exploitation.
  8. Regularly update and patch all related software and operating systems to reduce attack surface.

Description

Out of bounds read vulnerability due to improper bounds checking in NI LabVIEW in lvre!UDecStrToNum that 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 Q1 and prior versions.

References

Community reviews

Loading reviews…