Skip to main content
CVE-2025-7849VulnerabilityPublished Updated

CVE-2025-7849: NI LabVIEW · CWE-1285

Affects NI LabVIEWSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% 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 29 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
NI LabVIEWAffected
  • =0
  • =23.0.0
  • =24.0.0
  • =25.0.0
  • <=25.0.0
Fixed in–

AI-suggested

Organizations should implement the following specific mitigations: 1) Restrict the opening of VI files to trusted sources only and educate users about the risks of opening unverified VI files. 2) Employ application whitelisting and sandboxing techniques to limit the execution environment of LabVIEW and reduce the impact of potential exploitation. 3) Monitor and audit LabVIEW usage and file access to detect anomalous behavior indicative of exploitation attempts. 4) Coordinate with NI for timely patch deployment once an official fix is released; in the interim, consider disabling LabVIEW or limiting its use on high-risk endpoints. 5) Use endpoint detection and response (EDR) tools to identify suspicious memory corruption or code execution patterns related to LabVIEW processes. 6) Implement network segmentation to isolate systems running LabVIEW from broader corporate networks to contain potential breaches. These measures go beyond generic advice by focusing on controlling VI file handling, monitoring LabVIEW-specific activity, and preparing for patch deployment.

Description

A memory corruption vulnerability due to improper error handling when a VILinkObj is null 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. This vulnerability affects NI LabVIEW 2025 Q1 and prior versions.

References

Community reviews

Loading reviews…