dbcve.org
DasylabApplication · Ni

CVE-2026-0957

HIGH · 7.8 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
There is a memory corruption vulnerability due to an out-of-bounds write 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 open a specially crafted file. This vulnerability affects all versions of Digilent DASYLab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Memory corruption vulnerability in Digilent DASYLab caused by an out-of-bounds write when parsing corrupted files. Attackers can craft malicious files that trigger this memory corruption, potentially leading to information disclosure or arbitrary code execution upon user interaction.

MitigationAvoid opening untrusted or unverified files in DASYLab until a vendor patch is available. Implement file validation and consider application sandboxing to limit exploitation impact.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DasylabApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm DASYLab installation
    Check for DASYLab software on the system: Look for DASYLab in installed programs (Windows: Add/Remove Programs, Linux: dpkg -l or rpm -qa), or search for dasylab executable files in common installation directories like C:\Program Files\DASYLab or /opt/dasylab
    Affected if DASYLab is present on the system
  2. Identify DASYLab version
    Open DASYLab and navigate to Help > About, or check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\DASYLab for the Version key, or inspect the dasylab.exe file properties for version information
    Affected if Any version of DASYLab is installed (all versions are affected)
  3. Verify file import capability
    Confirm the file import/open functionality is accessible: Check if DASYLab can load data files through File > Open, File > Import, or drag-and-drop file loading. Also verify no application-level restrictions block file operations
    Affected if File import or open features are enabled and accessible to users
  4. Audit recent file operations
    Review recently opened or imported files in DASYLab: Check the application's recent files list (File > Recent), Windows Jump Lists, or examine any workflow/project files (.dsllab, .dsd) that may contain references to external data files
    Affected if Users have opened or can open external files in DASYLab
  5. Check for untrusted file sources
    Identify if DASYLab is configured to accept files from untrusted or external sources: Look for network-shared file locations, USB drives, or download folders configured as data sources, or check if the application has any file validation or sandboxing disabled
    Affected if DASYLab can open files from untrusted or unverified locations without validation

If DASYLab is installed and its file import/open feature is accessible, the environment is affected since all versions contain the vulnerability that triggers upon opening malicious crafted files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid opening untrusted or unverified files in DASYLab until a vendor patch is available. Implement file validation and consider application sandboxing to limit exploitation impact.

Fix this in Dasylab Scoped from the published advisory
  • Consultation6.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
48.0 hours of engineering $8,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,440.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0957 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0957 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data