<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: isync project</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2021-3657: A flaw was found in mbsync versions prior to 1.4.4</title><link>https://patchthecve.com/cve/CVE-2021-3657.html</link><guid>https://patchthecve.com/cve/CVE-2021-3657.html</guid><pubDate>Wed, 17 Jun 2026 04:05:31 +0000</pubDate><description>CRITICAL 9.8: A flaw was found in mbsync versions prior to 1.4.4. Due to inadequate handling of extremely large (&gt;=2GiB) IMAP literals, malicious or compromised IMAP servers, and hypothetically even external email senders, could cause several different buffer overflows, which could conceivably be exploited for re</description></item><item><title>CVE-2021-3578: A flaw was found in mbsync before v1.3.6 and v1.4.2, where an unchecked pointer cast allows a malicious or com</title><link>https://patchthecve.com/cve/CVE-2021-3578.html</link><guid>https://patchthecve.com/cve/CVE-2021-3578.html</guid><pubDate>Wed, 17 Jun 2026 04:05:22 +0000</pubDate><description>HIGH 7.8: A flaw was found in mbsync before v1.3.6 and v1.4.2, where an unchecked pointer cast allows a malicious or compromised server to write an arbitrary integer value past the end of a heap-allocated structure by issuing an unexpected APPENDUID response. This could be plausibly exploited for remote code </description></item><item><title>CVE-2021-44143: A flaw was found in mbsync in isync 1.4.0 through 1.4.3</title><link>https://patchthecve.com/cve/CVE-2021-44143.html</link><guid>https://patchthecve.com/cve/CVE-2021-44143.html</guid><pubDate>Wed, 17 Jun 2026 04:11:56 +0000</pubDate><description>CRITICAL 9.8: A flaw was found in mbsync in isync 1.4.0 through 1.4.3. Due to an unchecked condition, a malicious or compromised IMAP server could use a crafted mail message that lacks headers (i.e., one that starts with an empty line) to provoke a heap overflow, which could conceivably be exploited for remote co</description></item></channel></rss>