EUVD-2026-70769
GHSA-v5qj-5q4r-8fg9
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious .DSB file
-
DeliveryDeliver file via email or share
-
ExploitUser opens file in DASYLab
-
ExecutionHeap out-of-bounds write triggered
-
PersistHeap metadata corrupted
-
ImpactAttacker-controlled code executed
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a user with DASYLab installed to open a specially crafted .DSB file - this is the sole mandatory precondition. The attack vector is entirely local and file-based (AV:L, UI:P in CVSS 4.0); there is no network-reachable attack surface and no daemon or service to target remotely. The attacker does not need any authentication, account, or pre-existing system access. The principal limiting factor is the social-engineering step: the attacker must deliver the malicious file and persuade the victim to open it, which constrains automated or mass exploitation. No non-default configuration is required - any user who can open .DSB files in any DASYLab installation below 2026.0.0 is a valid target. |
| Impact | The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H) accurately reflects the threat model: exploitation is local and file-based, requiring passive user interaction (opening the .DSB file), but once triggered, impact is full compromise of the vulnerable system with high confidentiality, integrity, and availability loss. The low attack complexity and absence of any privilege requirement or special attack condition mean that even a mid-sized industrial IT team in walbrzych operating legacy DASYLab installations should treat this as urgent, since a single phishing email with a malicious .DSB attachment is a plausible delivery vector. No EPSS score is available in the input data, and neither CISA KEV listing nor public proof-of-concept code has been identified, which moderates the immediacy of mass exploitation risk. However, DASYLab's industrial/scientific user base - which may include operators less accustomed to treating data files as potential attack surfaces - elevates the social-engineering feasibility above average. The CVSS 4.0 score of 8.5 is appropriate given full triad impact, though the file-delivery dependency limits automated/opportunistic exploitation. |
| Exploit ScenarioDerived | An attacker crafts a malicious DASYLab .DSB project file with a heap-overflowing data field and delivers it to a target engineer or technician via email, USB drop, or a compromised file-sharing platform. The victim opens the file in their unpatched DASYLab installation, triggering the out-of-bounds write, which the attacker leverages via heap-shaping techniques to redirect execution and deploy a payload such as a reverse shell or data-exfiltration implant. No public proof-of-concept has been identified, but the well-understood CWE-787 class makes independent exploit development feasible for skilled adversaries. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 03, 2026
Out-of-bounds heap write in DASYLab before version 2026.0.0 enables arbitrary code execution on the victim's system when a user opens a maliciously crafted .DSB worksheet file. The flaw stems from insufficient validation of user-supplied data during .DSB file parsing, allowing an attacker to write past the end of an allocated heap buffer (CWE-787). All versions of DASYLab prior to 2026.0.0 are affected, and exploitation relies entirely on convincing a user to open a weaponized file; no public exploit or active exploitation has been identified at time of analysis.
RemediationAI
Upgrade to DASYLab 2026.0.0 or later, which resolves this vulnerability per the measX security advisory (https://www.measx.com/en/service/productsecurity/security-updates-for-measx-software/159-securityupdates/1071-out-of-bounds-write-vulnerabilities-in-dasylab-2.html). If immediate upgrade is not feasible, apply strict controls on .DSB file ingestion: disable automatic file opening from email attachments or network shares, restrict file handling to trusted internal sources only, and educate users not to open .DSB files received from unknown parties. Operating DASYLab in a sandboxed or restricted-privilege environment (e.g., via Windows AppLocker or similar application control) can limit the blast radius of a successful exploit by preventing code execution from reaching sensitive system resources or lateral movement paths. These workarounds carry the trade-off of operational friction for teams that routinely exchange project files with external partners.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
DASYLab is a graphical data acquisition and automation software product developed by measX (CPE: cpe:2.3:a:measx:dasylab:*:*:*:*:*:*:*:*), historically distributed through National Instruments (NI). The .DSB file format is DASYLab's native project/worksheet format. CWE-787 (Out-of-Bounds Write) indicates that during parsing of a crafted .DSB file, the application writes data beyond the boundary of a heap-allocated buffer due to missing or inadequate length/bounds checks on attacker-controlled input fields. Heap out-of-bounds writes of this class can corrupt adjacent heap metadata or object pointers, typically enabling attacker-controlled code execution via heap-layout manipulation techniques. The vulnerability is fully client-side, triggered at file parse time, with no network service or daemon involvement.
Know when Dasylab gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
File-open trigger requires user interaction (UI:R) and local execution (AV:L); no privileges or special configuration needed, with full triad impact on the vulnerable host.
Primary rating from Vendor (NI).
CVSS VectorVendor: NI
Lifecycle Timeline
2DescriptionCVE.org
There is an out-of-bounds write vulnerability in DASYLab due to improper validation of user-supplied data, resulting in a write past the end of an allocated heap. Successful exploitation requires an attacker to get a user to open a specially crafted .DSB file. This issue affects all versions before 2026.0.0.
Executive ViewAI
DASYLab measurement and data acquisition software versions before 2026.0.0 contain an out-of-bounds heap write vulnerability enabling arbitrary code execution when users open malicious .DSB worksheet files. Organizations deploying DASYLab face potential system compromise and operational disruption if users encounter adversarially crafted files, particularly from external email or file-sharing channels lacking proper validation.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) restrict .DSB file access to vetted internal sources only and disable file associations for shared or guest accounts; (2) execute DASYLab in application-level sandboxes or isolated VM environments; (3) block .DSB attachments at email gateways for external senders; (4) maintain verified offline backups of critical data independent of systems running affected DASYLab versions.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
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 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
There is an out of bounds write vulnerability due to improper bounds checking resulting in invalid data when parsing a D
Exploit-DB