EUVD-2026-12041Severity by source
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionCVE.org
There is a memory corruption vulnerability due to an out-of-bounds read when loading a corrupted file in Digilent DASYLab. This vulnerability may result in information disclosure or arbitrary code execution. Successful exploitation requires an attacker to get a user to open a specially crafted file. This vulnerability affects all versions of Digilent DASYLab.
AnalysisAI
Memory corruption vulnerability in all versions of Digilent DASYLab data acquisition software that occurs when processing maliciously crafted files, potentially allowing attackers to leak sensitive information or execute arbitrary code. The vulnerability requires user interaction (opening a malicious file) and has a CVSS score of 7.8, with no current evidence of active exploitation or public proof-of-concept code.
Technical ContextAI
DASYLab is a data acquisition and analysis software used for measurement and control applications. The vulnerability stems from an out-of-bounds read (CWE-125) memory corruption issue when the application parses corrupted or malformed files. Based on the CPE string (cpe:2.3:a:digilent:dasylab:*:*:*:*:*:*:*:*), all versions of DASYLab are affected. CWE-125 vulnerabilities occur when software reads data past the end of allocated memory buffers, potentially exposing sensitive data or causing crashes that can be leveraged for code execution.
RemediationAI
As of the current intelligence, no patch information is available in the provided data. Users should immediately review the National Instruments security advisory (https://www.ni.com/en/support/security/available-critical-and-security-updates-for-ni-software/2026/out-of-bounds-read-vulnerabilities-in-digilent-dasylab.html) for patch availability and update instructions. Until patches are applied, implement these mitigations: (1) Restrict opening DASYLab files to trusted sources only, (2) Implement application sandboxing where possible, (3) Use endpoint detection systems to monitor for suspicious DASYLab process behavior, (4) Train users on social engineering attacks involving malicious files.
Out-of-bounds memory read in DASYLab's .DSB file parser (all versions before 2026.0.0) allows an attacker to read beyond
There is a deserialization of untrusted data vulnerability in Digilent DASYLab. Rated high severity (CVSS 8.5), this vul
Out-of-bounds heap read in DASYLab's .DSB file parser allows memory disclosure and potentially code execution when a vic
Out-of-bounds heap read during .DSB file parsing in DASYLab (all versions prior to 2026.0.0) allows an attacker who can
Out-of-bounds write in DASYLab (all versions before 2026.0.0) enables arbitrary code execution when a victim opens a spe
Out-of-bounds heap write in DASYLab before version 2026.0.0 enables arbitrary code execution on the victim's system when
Out-of-bounds write in DASYLab's .DSB worksheet file parser allows an attacker to achieve code execution with full confi
There is an out of bounds write vulnerability due to improper bounds checking resulting in a large destination address w
There is an out of bounds write vulnerability due to improper bounds checking resulting in an invalid source address whe
There is an out of bounds write vulnerability due to improper bounds checking in displ2.dll when parsing a DSB file with
There is an out of bounds write vulnerability due to improper bounds checking resulting in an invalid address when parsi
There is a heap-based Buffer Overflow vulnerability due to improper bounds checking when parsing a DSB file with Digilen
Same weakness CWE-125 – Out-of-bounds Read
View allShare
External POC / Exploit Code
Leaving vuln.today