Code execution via improper VI index validation
Published Jul 29, 2025 · Updated Feb 26, 2026
Memory corruption in lvpict.cpp in NI LabVIEW 2025 Q1 and earlier allows attackers to execute code through a crafted VI file. The lvpict.cpp parser fails to validate a specified index, position, or offset before using it while processing the VI, corrupting memory. Exploitation requires a user to open the attacker-supplied file, after which code can execute in the LabVIEW process context.
Summary
What happened
Memory corruption in lvpict.cpp in NI LabVIEW 2025 Q1 and earlier allows attackers to execute code through a crafted VI file. The lvpict.cpp parser fails to validate a specified index, position, or offset before using it while processing the VI, corrupting memory. Exploitation requires a user to open the attacker-supplied file, after which code can execute in the LabVIEW process context.
The record
- CVE
- CVE-2025-7848
- Published
- Jul 29, 2025
- Updated
- Feb 26, 2026
- Vendor
- National Instruments
- Product
- LabVIEW
- Classifications
- CWE-1285, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=22.3.5
- Affected versionversion=23.0.0 <=23.3.6
- Affected versionversion=24.0.0 <=24.3.3
- Affected versionversion=25.0.0 <25.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo