<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: ezxml</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2022-30045: An issue was discovered in libezxml.a in ezXML 0.8.6</title><link>https://patchthecve.com/cve/CVE-2022-30045.html</link><guid>https://patchthecve.com/cve/CVE-2022-30045.html</guid><pubDate>Wed, 17 Jun 2026 04:43:00 +0000</pubDate><description>MEDIUM 6.5: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_decode() performs incorrect memory handling while parsing crafted XML files, leading to a heap out-of-bounds read.</description></item><item><title>CVE-2021-31598: An issue was discovered in libezxml.a in ezXML 0.8.6</title><link>https://patchthecve.com/cve/CVE-2021-31598.html</link><guid>https://patchthecve.com/cve/CVE-2021-31598.html</guid><pubDate>Wed, 17 Jun 2026 03:52:03 +0000</pubDate><description>HIGH 7.5: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_decode() performs incorrect memory handling while parsing crafted XML files, leading to a heap-based buffer overflow.</description></item><item><title>CVE-2021-31348: An issue was discovered in libezxml.a in ezXML 0.8.6</title><link>https://patchthecve.com/cve/CVE-2021-31348.html</link><guid>https://patchthecve.com/cve/CVE-2021-31348.html</guid><pubDate>Wed, 17 Jun 2026 03:51:35 +0000</pubDate><description>MEDIUM 6.5: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_parse_str() performs incorrect memory handling while parsing crafted XML files (out-of-bounds read after a certain strcspn failure).</description></item><item><title>CVE-2021-31347: An issue was discovered in libezxml.a in ezXML 0.8.6</title><link>https://patchthecve.com/cve/CVE-2021-31347.html</link><guid>https://patchthecve.com/cve/CVE-2021-31347.html</guid><pubDate>Wed, 17 Jun 2026 03:51:35 +0000</pubDate><description>MEDIUM 6.5: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_parse_str() performs incorrect memory handling while parsing crafted XML files (writing outside a memory region created by mmap).</description></item><item><title>CVE-2021-31229: An issue was discovered in libezxml.a in ezXML 0.8.6</title><link>https://patchthecve.com/cve/CVE-2021-31229.html</link><guid>https://patchthecve.com/cve/CVE-2021-31229.html</guid><pubDate>Wed, 17 Jun 2026 03:51:29 +0000</pubDate><description>MEDIUM 6.5: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_internal_dtd() performs incorrect memory handling while parsing crafted XML files, which leads to an out-of-bounds write of a one byte constant.</description></item><item><title>CVE-2021-26222: The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhau</title><link>https://patchthecve.com/cve/CVE-2021-26222.html</link><guid>https://patchthecve.com/cve/CVE-2021-26222.html</guid><pubDate>Wed, 17 Jun 2026 03:42:58 +0000</pubDate><description>HIGH 8.1: The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.</description></item><item><title>CVE-2021-26221: The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhau</title><link>https://patchthecve.com/cve/CVE-2021-26221.html</link><guid>https://patchthecve.com/cve/CVE-2021-26221.html</guid><pubDate>Wed, 17 Jun 2026 03:42:58 +0000</pubDate><description>HIGH 8.1: The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.</description></item><item><title>CVE-2021-26220: The ezxml_toxml function in ezxml 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exh</title><link>https://patchthecve.com/cve/CVE-2021-26220.html</link><guid>https://patchthecve.com/cve/CVE-2021-26220.html</guid><pubDate>Wed, 17 Jun 2026 03:42:57 +0000</pubDate><description>HIGH 8.1: The ezxml_toxml function in ezxml 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.</description></item><item><title>CVE-2019-20202: An issue was discovered in ezXML 0.8.3 through 0.8.6</title><link>https://patchthecve.com/cve/CVE-2019-20202.html</link><guid>https://patchthecve.com/cve/CVE-2019-20202.html</guid><pubDate>Wed, 17 Jun 2026 02:30:11 +0000</pubDate><description>MEDIUM 6.5: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_char_content() tries to use realloc on a block that was not allocated, leading to an invalid free and segmentation fault.</description></item><item><title>CVE-2019-20201: An issue was discovered in ezXML 0.8.3 through 0.8.6</title><link>https://patchthecve.com/cve/CVE-2019-20201.html</link><guid>https://patchthecve.com/cve/CVE-2019-20201.html</guid><pubDate>Wed, 17 Jun 2026 02:30:11 +0000</pubDate><description>MEDIUM 6.5: An issue was discovered in ezXML 0.8.3 through 0.8.6. The ezxml_parse_* functions mishandle XML entities, leading to an infinite loop in which memory allocations occur.</description></item><item><title>CVE-2019-20200: An issue was discovered in ezXML 0.8.3 through 0.8.6</title><link>https://patchthecve.com/cve/CVE-2019-20200.html</link><guid>https://patchthecve.com/cve/CVE-2019-20200.html</guid><pubDate>Wed, 17 Jun 2026 02:30:11 +0000</pubDate><description>MEDIUM 6.5: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing crafted a XML file, performs incorrect memory handling, leading to a heap-based buffer over-read in the &quot;normalize line endings&quot; feature.</description></item><item><title>CVE-2019-20199: An issue was discovered in ezXML 0.8.3 through 0.8.6</title><link>https://patchthecve.com/cve/CVE-2019-20199.html</link><guid>https://patchthecve.com/cve/CVE-2019-20199.html</guid><pubDate>Wed, 17 Jun 2026 02:30:11 +0000</pubDate><description>MEDIUM 6.5: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing a crafted XML file, performs incorrect memory handling, leading to NULL pointer dereference while running strlen() on a NULL pointer.</description></item><item><title>CVE-2019-20198: An issue was discovered in ezXML 0.8.3 through 0.8.6</title><link>https://patchthecve.com/cve/CVE-2019-20198.html</link><guid>https://patchthecve.com/cve/CVE-2019-20198.html</guid><pubDate>Wed, 17 Jun 2026 02:30:11 +0000</pubDate><description>MEDIUM 6.5: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_ent_ok() mishandles recursion, leading to stack consumption for a crafted XML file.</description></item><item><title>CVE-2019-20007: An issue was discovered in ezXML 0.8.2 through 0.8.6</title><link>https://patchthecve.com/cve/CVE-2019-20007.html</link><guid>https://patchthecve.com/cve/CVE-2019-20007.html</guid><pubDate>Wed, 17 Jun 2026 02:29:49 +0000</pubDate><description>MEDIUM 6.5: An issue was discovered in ezXML 0.8.2 through 0.8.6. The function ezxml_str2utf8, while parsing a crafted XML file, performs zero-length reallocation in ezxml.c, leading to returning a NULL pointer (in some compilers). After this, the function ezxml_parse_str does not check whether the s variable i</description></item><item><title>CVE-2019-20006: An issue was discovered in ezXML 0.8.3 through 0.8.6</title><link>https://patchthecve.com/cve/CVE-2019-20006.html</link><guid>https://patchthecve.com/cve/CVE-2019-20006.html</guid><pubDate>Wed, 17 Jun 2026 02:29:49 +0000</pubDate><description>HIGH 7.5: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_char_content puts a pointer to the internal address of a larger block as xml-&gt;txt. This is later deallocated (using free), leading to a segmentation fault.</description></item><item><title>CVE-2019-20005: An issue was discovered in ezXML 0.8.3 through 0.8.6</title><link>https://patchthecve.com/cve/CVE-2019-20005.html</link><guid>https://patchthecve.com/cve/CVE-2019-20005.html</guid><pubDate>Wed, 17 Jun 2026 02:29:49 +0000</pubDate><description>MEDIUM 6.5: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing a crafted XML file, performs incorrect memory handling, leading to a heap-based buffer over-read while running strchr() starting with a pointer after a &#x27;\0&#x27; character (where the processing of a string was </description></item></channel></rss>