EUVD-2026-12035Severity 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
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
3DescriptionCVE.org
There is a memory corruption vulnerability due to an out-of-bounds write when loading a corrupted DSB 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 .DSB file. This vulnerability affects all versions of Digilent DASYLab.
AnalysisAI
Memory corruption vulnerability in all versions of Digilent DASYLab data acquisition software that allows attackers to achieve arbitrary code execution or information disclosure by tricking users into opening malicious .DSB files. With a CVSS score of 7.8 and requiring only user interaction, this out-of-bounds write vulnerability poses significant risk, though no active exploitation or public POCs have been reported.
Technical ContextAI
DASYLab is a data acquisition and analysis software used in industrial and research environments for processing sensor data and control systems. The vulnerability stems from improper bounds checking when parsing DSB (DASYLab native) project files, resulting in CWE-787 (Out-of-bounds Write) - a classic memory safety issue where data is written beyond allocated buffer boundaries. Based on the CPE string (cpe:2.3:a:digilent:dasylab:*:*:*:*:*:*:*:*), all versions of the software are affected, suggesting a fundamental parsing flaw in the DSB file format handler.
RemediationAI
As of the advisory date, no patches are available for any DASYLab version. Primary mitigation involves user awareness training to avoid opening untrusted .DSB files. Organizations should implement email/file filtering for .DSB attachments, restrict DASYLab to isolated systems where possible, and monitor the NI security advisory (https://www.ni.com/en/support/security/available-critical-and-security-updates-for-ni-software/2026/out-of-bounds-write-vulnerabilities-in-digilent-dasylab.html) for patch availability. Consider using application sandboxing or virtualization when processing external DSB files.
There is a deserialization of untrusted data vulnerability in Digilent DASYLab. Rated high severity (CVSS 8.5), this vul
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
There is an out of bounds write vulnerability due to improper bounds checking resulting in invalid data when parsing a D
Memory corruption vulnerability in all versions of Digilent DASYLab data acquisition software that occurs when processin
Memory corruption vulnerability in all versions of Digilent DASYLab software that allows attackers to achieve informatio
Memory corruption vulnerability in all versions of Digilent DASYLab that allows attackers to execute arbitrary code or s
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
Same weakness CWE-787 – Out-of-bounds Write
View allSame technique Buffer Overflow
View allShare
External POC / Exploit Code
Leaving vuln.today