Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-0956: CWE-125 Out-of-bounds read in Digilent DASYLab

0
High
VulnerabilityCVE-2026-0956cvecve-2026-0956cwe-125
Published: Fri Mar 13 2026 (03/13/2026, 15:11:31 UTC)
Source: CVE Database V5
Vendor/Project: Digilent
Product: DASYLab

Description

CVE-2026-0956 is a high-severity memory corruption vulnerability in Digilent DASYLab caused by an out-of-bounds read when loading a specially crafted corrupted file. Exploitation requires user interaction to open the malicious file, potentially leading to information disclosure or arbitrary code execution. This vulnerability affects all versions of DASYLab and has a CVSS score of 7. 8, reflecting its significant impact on confidentiality, integrity, and availability. No known exploits are currently reported in the wild. Organizations using DASYLab should be cautious about opening untrusted files and monitor for updates or patches from Digilent. The vulnerability poses a risk primarily to environments where DASYLab is used, including engineering, scientific, and industrial sectors worldwide. Mitigation involves restricting file sources, applying any future patches promptly, and employing endpoint protections to detect suspicious file activity.

AI-Powered Analysis

AILast updated: 03/13/2026, 15:44:05 UTC

Technical Analysis

CVE-2026-0956 is a vulnerability identified in Digilent's DASYLab software, a tool widely used for data acquisition and control applications. The root cause is an out-of-bounds read (CWE-125) triggered when the software attempts to load a corrupted file. This memory corruption flaw can lead to serious consequences, including unauthorized disclosure of sensitive information or execution of arbitrary code, which could allow an attacker to take control of the affected system. Exploitation requires that an attacker craft a malicious file and convince a user to open it, making user interaction necessary. The vulnerability affects all versions of DASYLab, indicating a fundamental flaw in the file parsing logic. The CVSS v3.1 base score of 7.8 reflects a high severity level, with attack vector local (AV:L), low attack complexity (AC:L), no privileges required (PR:N), user interaction required (UI:R), and high impact on confidentiality, integrity, and availability (C:H/I:H/A:H). Although no public exploits are known, the potential for severe damage warrants immediate attention. The lack of available patches at the time of publication means users must rely on mitigation strategies until official fixes are released.

Potential Impact

The vulnerability can have significant impacts on organizations using DASYLab, particularly in sectors relying on precise data acquisition and control such as manufacturing, research laboratories, and industrial automation. Successful exploitation could lead to leakage of sensitive data, disruption of critical processes, or full system compromise, undermining operational integrity and confidentiality. Given the high impact on confidentiality, integrity, and availability, attackers could manipulate data outputs or disrupt system functions, potentially causing financial loss, safety hazards, or reputational damage. The requirement for user interaction limits remote exploitation but does not eliminate risk, especially in environments where users may open files from untrusted sources. The absence of known exploits currently reduces immediate threat but does not preclude future attacks as exploit code may be developed. Organizations worldwide using DASYLab are at risk until mitigations or patches are applied.

Mitigation Recommendations

1. Educate users to avoid opening files from untrusted or unknown sources, especially in environments where DASYLab is used. 2. Implement strict file validation and scanning policies at email gateways and endpoint security solutions to detect and block malicious files targeting this vulnerability. 3. Employ application whitelisting and sandboxing techniques to limit the impact of potential exploitation. 4. Monitor for updates from Digilent and apply patches promptly once available. 5. Consider network segmentation to isolate systems running DASYLab from general user environments to reduce exposure. 6. Use endpoint detection and response (EDR) tools to identify suspicious behavior indicative of exploitation attempts. 7. Maintain regular backups of critical data and system configurations to enable recovery in case of compromise. 8. If feasible, restrict DASYLab usage to trusted personnel and environments to minimize risk of malicious file introduction.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
NI
Date Reserved
2026-01-14T19:16:24.636Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69b42da82f860ef943f7d604

Added to database: 3/13/2026, 3:30:48 PM

Last enriched: 3/13/2026, 3:44:05 PM

Last updated: 3/13/2026, 5:49:30 PM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses