EUVD-2026-70770
GHSA-28jj-q8cg-6fc9
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious .DSB worksheet file
-
DeliveryDeliver file via email or file share
-
ExploitVictim opens file in unpatched DASYLab
-
ExecutionOut-of-bounds write corrupts heap/stack
-
ImpactArbitrary code execution as victim user
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 the victim to open a specially crafted .DSB file in DASYLab version prior to 2026.0.0 - there is no remote unauthenticated or network-based exploitation path. The attacker must first deliver the malicious file and persuade the user to open it (social engineering). Limiting factors: the local/file-open attack vector eliminates remote exploitation; user interaction is required; the affected user base is narrow (industrial engineers and scientists using specialized DAQ software); and no default network service or exposed API is involved. Organizations whose users do not receive or process externally sourced .DSB files face minimal realistic exposure. |
| Impact | The CVSS 4.0 score of 8.5 with vector AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H accurately reflects the local file-open requirement and high impact. The local attack vector (AV:L) and mandatory user interaction (UI:P - opening the file) meaningfully reduce exploitability relative to remote or zero-click vulnerabilities. No EPSS data, CISA KEV listing, or public proof-of-concept code has been identified, so exploitation ease and urgency are inferred from the CVSS vector and CWE class alone. The niche industrial and scientific deployment footprint of DASYLab limits mass exploitation scenarios; realistic risk centers on targeted delivery of malicious .DSB files to engineers, researchers, or laboratory technicians. The high C/I/A impact scores are plausible for a memory corruption class enabling code execution, but actual impact is gated behind successful social engineering. |
| Exploit ScenarioDerived | An attacker crafts a .DSB worksheet file with malformed data structures that trigger the out-of-bounds write when loaded by DASYLab's parser. The file is delivered to a target engineer or scientist via spear-phishing email, a compromised file share, or a poisoned project archive, then the victim opens it in an unpatched DASYLab installation. Successful exploitation results in arbitrary code execution under the victim's user account. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 03, 2026
Out-of-bounds write in DASYLab (all versions before 2026.0.0) enables arbitrary code execution when a victim opens a specially crafted .DSB worksheet file. The flaw, CWE-787, stems from improper validation of user-supplied data within the .DSB file parser, permitting writes past the end of an allocated data structure and corrupting adjacent memory. No public exploit or active exploitation has been identified at time of analysis; successful exploitation requires social-engineering the target into opening a malicious file.
RemediationAI
Upgrade DASYLab to version 2026.0.0 or later, which resolves this out-of-bounds write vulnerability per the measX security advisory at https://www.measx.com/en/service/productsecurity/security-updates-for-measx-software/159-securityupdates/1071-out-of-bounds-write-vulnerabilities-in-dasylab-2.html. Where immediate patching is not feasible, apply the following compensating controls: block or quarantine inbound .DSB file attachments at the email gateway to prevent phishing delivery; restrict .DSB file exchange to verified internal project repositories with access controls; and train users not to open .DSB files from unverified or external sources. Note that these controls reduce the social-engineering delivery vector but do not eliminate the underlying parser vulnerability - patching remains the definitive fix.
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 proprietary graphical data acquisition and analysis platform from measX (formerly distributed by NI/National Instruments), used in engineering, manufacturing, and scientific laboratory environments. The .DSB file format is DASYLab's native worksheet format that encodes experimental configurations, data flows, and instrument setups. The vulnerability (CWE-787, Out-of-Bounds Write) resides in the .DSB file parser: user-supplied values from the file are not adequately bounds-checked before being written into an allocated data structure, allowing writes past its end. This class of flaw commonly enables control-flow hijacking, heap corruption, or stack smashing leading to arbitrary code execution. CPE cpe:2.3:a:measx:dasylab:*:*:*:*:*:*:*:* confirms measX as the current product owner.
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 must be opened locally by the victim (AV:L/UI:R); no attacker authentication required; out-of-bounds write class yields full local code execution potential (C:H/I:H/A:H).
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 data structure. 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 versions before 2026.0.0 contain a critical out-of-bounds write vulnerability (CVE-2026-64197) enabling arbitrary code execution when users open malicious worksheet files; no public exploit identified at time of analysis. Organizations using DASYLab face risk from social-engineered attacks delivering malicious .DSB files. No vendor patch is currently available, requiring immediate user awareness and interim defensive measures.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict DASYLab system access to authorized personnel only; mandate security training for all DASYLab users on risks of opening untrusted files; segment DASYLab workstations from mission-critical systems using network isolation; disable auto-execution of embedded content in .DSB files if the feature is available; monitor DASYLab processes for abnormal behavior including memory corruption indicators, unexpected child process creation, or unauthorized privilege escalation attempts.
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 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
There is an out of bounds write vulnerability due to improper bounds checking resulting in invalid data when parsing a D
Exploit-DB