CVE-2025-7848: NI LabVIEW · Improper Validation of Specified Index, Position, or Offset in Input
Affects NI LabVIEWSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 5.7% chance of exploitation in 30 days – higher than 92% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| NI LabVIEW | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-7848, organizations should implement the following specific measures: 1) Immediately restrict access to VI files from untrusted sources and educate users about the risks of opening unsolicited or unknown VI files. 2) Employ application whitelisting and sandboxing techniques to limit LabVIEW's ability to execute arbitrary code outside intended environments. 3) Monitor and audit file access and execution logs for unusual activity related to VI files. 4) Use endpoint protection solutions capable of detecting memory corruption exploits and anomalous process behavior. 5) Coordinate with NI for timely patches or updates addressing this vulnerability and apply them as soon as they become available. 6) Implement network segmentation to isolate systems running LabVIEW from less secure network zones to reduce attack surface. 7) Develop incident response plans specific to LabVIEW compromise scenarios to enable rapid containment and recovery. These steps go beyond generic advice by focusing on controlling VI file handling, leveraging LabVIEW-specific operational practices, and preparing for targeted incident response.
Description
A memory corruption vulnerability due to improper input validation in lvpict.cpp 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.