Cyber Resilience

CVE-2026-0955

Memory Safety in Ni Dasylab

Memory Safety
Published
13 March 2026
Modified
19 March 2026
Patch / advisory
View advisory
CVSS Score v4 8.5
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0020 10th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-0955 is a high-severity Out-of-bounds Read (CWE-125) vulnerability in Ni Dasylab. Its CVSS base score is 8.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-0955 is a memory corruption vulnerability stemming from an out-of-bounds read (CWE-125) in Digilent DASYLab, occurring when loading a corrupted file. This flaw affects all versions of the software and carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Successful exploitation could lead to information disclosure or arbitrary code execution.

The vulnerability can be exploited by an attacker with local access who tricks a user into opening a specially crafted file within Digilent DASYLab. No privileges are required on the part of the attacker, but user interaction is necessary, making it a socially engineered local attack vector. Upon exploitation, an attacker could achieve high-impact confidentiality, integrity, and availability violations, potentially compromising the affected system.

The National Instruments (NI) security advisory at 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 details available critical and security updates for addressing out-of-bounds read vulnerabilities in Digilent DASYLab. Security practitioners should consult this reference for patch information and mitigation guidance.

EU & UK References

Vulnerability Data

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…

more

open a specially crafted file. This vulnerability affects all versions of Digilent DASYLab.

CWE(s)
CWE-125

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-0956Same product: Ni Dasylab
CVE-2025-9189Same product: Ni Dasylab
CVE-2025-57776Same product: Ni Dasylab
CVE-2026-0957Same product: Ni Dasylab
CVE-2025-57777Same product: Ni Dasylab
CVE-2025-57778Same product: Ni Dasylab
CVE-2025-57774Same product: Ni Dasylab
CVE-2025-57775Same product: Ni Dasylab
CVE-2026-0954Same product: Ni Dasylab
CVE-2025-9188Same product: Ni Dasylab

Affected Assets

ni
dasylab
all versions

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation directly finds out-of-bounds read flaws through static analysis, fuzzing, and dynamic bounds checks.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require bounds checking and memory-safe constructs that stop out-of-bounds reads from being introduced.

SC-39 Process Isolation partial match

Process isolation confines the effects of an out-of-bounds read to the compromised process.

SI-10 Information Input Validation partial match

Input validation rejects malformed indices or lengths that would otherwise cause reads outside buffer bounds.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.

PR.PS-02 partial match
prevents

Routine patching replaces vulnerable code containing out-of-bounds read flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.

A.8.15 Logging partial match
finds

Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.

References