<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: dasylab</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2026-64200: There is an out-of-bounds read vulnerability in DASYLab due to improper validation of user-supplied data</title><link>https://patchthecve.com/cve/CVE-2026-64200.html</link><guid>https://patchthecve.com/cve/CVE-2026-64200.html</guid><pubDate>Tue, 22 Sep 2026 18:29:21 +0000</pubDate><description>HIGH 7.8: There is an out-of-bounds read vulnerability in DASYLab due to improper validation of user-supplied data.   This results in a read a past the end of an allocated heap buffer during string conversion.  Successful exploitation requires an attacker to get a user to open a specially crafted .DSB file.  </description></item><item><title>CVE-2026-64199: There is an out-of-bounds read vulnerability in DASYLab due to improper validation of user-supplied data</title><link>https://patchthecve.com/cve/CVE-2026-64199.html</link><guid>https://patchthecve.com/cve/CVE-2026-64199.html</guid><pubDate>Tue, 22 Sep 2026 18:31:35 +0000</pubDate><description>HIGH 7.8: There is an out-of-bounds read vulnerability in DASYLab due to improper validation of user-supplied data.   This results in a read outside the bounds of an allocated data structure.  Successful exploitation requires an attacker to get a user to open a specially crafted .DSB file.  This issue affects</description></item><item><title>CVE-2026-64198: There is an out-of-bounds read vulnerability in DASYLab due to improper validation of user-supplied data</title><link>https://patchthecve.com/cve/CVE-2026-64198.html</link><guid>https://patchthecve.com/cve/CVE-2026-64198.html</guid><pubDate>Tue, 22 Sep 2026 18:32:00 +0000</pubDate><description>HIGH 7.8: There is an out-of-bounds read vulnerability in DASYLab due to improper validation of user-supplied data.   This results in a read a few bytes past the end of an allocated heap buffer during file handling.  Successful exploitation requires an attacker to get a user to open a specially crafted .DSB f</description></item><item><title>CVE-2026-64197: There is an out-of-bounds write vulnerability in DASYLab due to improper validation of user-supplied data, res</title><link>https://patchthecve.com/cve/CVE-2026-64197.html</link><guid>https://patchthecve.com/cve/CVE-2026-64197.html</guid><pubDate>Tue, 22 Sep 2026 18:33:22 +0000</pubDate><description>HIGH 7.8: 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 versi</description></item><item><title>CVE-2026-64196: There is an out-of-bounds write vulnerability in DASYLab due to improper validation of user-supplied data, res</title><link>https://patchthecve.com/cve/CVE-2026-64196.html</link><guid>https://patchthecve.com/cve/CVE-2026-64196.html</guid><pubDate>Tue, 22 Sep 2026 18:33:39 +0000</pubDate><description>HIGH 7.8: 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 heap. Successful exploitation requires an attacker to get a user to open a specially crafted .DSB file.  This issue affects all versions before</description></item><item><title>CVE-2026-64195: There is an out-of-bounds write vulnerability in DASYLab due to lack of proper validation of user-supplied dat</title><link>https://patchthecve.com/cve/CVE-2026-64195.html</link><guid>https://patchthecve.com/cve/CVE-2026-64195.html</guid><pubDate>Tue, 22 Sep 2026 18:34:00 +0000</pubDate><description>HIGH 7.8: There is an out-of-bounds write vulnerability in DASYLab due to lack of proper validation of user-supplied data. 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.</description></item></channel></rss>