DASYLab CVE-2026-64198

Exploitation requires that a user opens a specially crafted .DSB file in DASYLab running any version prior to 2026.0.0. The attacker must successfully deliver the malicious file to the target machine and persuade the user to open it (UI:P - passive user interaction is mandatory). No special privileges are required of the attacker or the victim's account. The attack vector is local (AV:L): the crafted file must be present on the local filesystem or a mounted network share at the time of opening. No network-reachable attack surface exists without prior file delivery and user interaction. Exploitation is limited to platforms where DASYLab is installed and the target uses .DSB file workflows.

The provided CVSS 4.0 score of 8.5 with VC:H/VI:H/VA:H warrants scrutiny: a pure out-of-bounds read of a few bytes past a heap buffer boundary realistically yields heap information disclosure (C:H) and a potential crash (A:H), but integrity impact (VI:H) is difficult to reconcile with the description, which does not suggest memory writes or code execution - this metric appears overstated unless the OOB read enables a secondary exploitation primitive not described. The attack vector (AV:L, UI:P) requires a user to manually open a malicious file, substantially reducing automatable risk; no public exploit code exists and the CVE is absent from CISA KEV, putting real-world exploitation likelihood low at this time. Even a mid-sized industrial measurement team in gdynia using DASYLab worksheets shared across a network share would need targeted social-engineering to expose users to crafted .DSB files, placing this squarely in the category of targeted rather than opportunistic threat. The EPSS score is not provided, but absence of KEV listing and file-open prerequisite suggest low population-level exploitation probability. Priority is moderate: upgrade to 2026.0.0 where feasible; restrict untrusted file ingestion in high-sensitivity environments.

An attacker crafts a malicious .DSB file with an oversized or malformed field that causes DASYLab's file parser to read a few bytes beyond a heap allocation boundary. The attacker delivers the file via email, a shared network drive, or a download link and convinces a DASYLab operator to open it. Upon opening, the application reads adjacent heap memory - potentially exposing sensitive runtime data - and may crash, causing a denial of service to the measurement session.