{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-64197 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-64197 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-64197 is a high-severity memory corruption vulnerability in measX DASYLab, published on 3 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-64197 and fix it if it is affected.\n\nWhat it is: CVE-2026-64197 is a high-severity memory corruption vulnerability in measX DASYLab, published on 3 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-64197 in the wild and no public exploit code.\n\nAffected product: measX DASYLab. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-64197/ (Markdown: https://insights.sbomify.com/CVE-2026-64197/index.md)","id":"CVE-2026-64197","markdown":"https://insights.sbomify.com/CVE-2026-64197/index.md","name":"CVE-2026-64197","record":{"aliases":["GHSA-28jj-q8cg-6fc9"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"DASYLab data acquisition","requires_auth":"none","summary":"An attacker can execute arbitrary code by tricking a user into opening a malicious .DSB file in DASYLab due to an out-of-bounds write vulnerability.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NI","cpe":[{"product":"dasylab","vendor":"ni"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"There is an out-of-bounds write vulnerability in DASYLab due to improper validation of user-supplied data, resulting in a write past the end of an allocated data structure. Successful exploitation requires an attacker to get a user to open a specially crafted .DSB file.  This issue affects all versions before 2026.0.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in DASYLab","id":"CVE-2026-64197","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Out Of Bounds Read in file handling when parsing a .DSB file in DASYLab","id":"CVE-2026-64198"},"packages":[],"prev":{"headline":"Memory corruption in DASYLab","id":"CVE-2026-64196"},"products":["DASYLab"],"published":"2026-09-03","related":[{"cvss_score":8.6,"headline":"Out Of Bounds Read outside the bounds of an allocated data structure when parsing a .DSB file in DASYLab","id":"CVE-2026-64199","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":8.5,"headline":"Out Of Bounds Write parsing a .DSB file in DASYLab due to lack of proper validation of user-supplied data","id":"CVE-2026-64195","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":8.5,"headline":"Memory corruption in DASYLab","id":"CVE-2026-64196","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":8.5,"headline":"Out Of Bounds Read in file handling when parsing a .DSB file in DASYLab","id":"CVE-2026-64198","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":8.5,"headline":"Out Of Bounds Read in during string conversionwhen parsing a .DSB file in DASYLab","id":"CVE-2026-64200","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":8.5,"headline":"Out-Of-Bounds Write When Opening a Corrupt DSB File in Digilent DASYLab","id":"CVE-2026-0954","kev_date_added":null,"published":"2026-03-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-04","vendors":["measX"]},"summary":"An attacker can execute arbitrary code by tricking a user into opening a malicious .DSB file in DASYLab due to an out-of-bounds write vulnerability.","url":"https://insights.sbomify.com/CVE-2026-64197/"}