CVE-2026-76957Medium 4.9libexpat before 2.8.4 lacks handler call depth tracking with custom encoding callbacks. Thus, a use-after-free can occur. NOTE: this is similar to CVE-2026-50219, CVE-2026-56131 and CVE-2026-56412.0.1%
CVE-2026-76956Medium 5.9In libexpat 2.8.2 and 2.8.3 before 2.8.4, misinterpretation of getentropy's return code leads to insufficient entropy, which results in being vulnerable to hash flooding attacks, causing a denial of s0.3%
CVE-2026-66046High 7.5Expat Denial of Service via storeAtts() Quadratic Complexity0.7%
CVE-2026-72522Medium 6.2libexpat before 2.8.3 has an out-of-bounds read and resultant infinite loop because low surrogates are treated the same as high surrogates during Unicode processing in the *_toUtf16 functions.0.2%
CVE-2026-56412Medium 4.9libexpat before 2.8.2 does not consider XML_TOK_DATA_CHARS in doCdataSection and thus lacks handler call depth tracking for various calls from within handlers in cases of a policy violation. Thus, a u0.2%
CVE-2026-56411Medium 6.9xmlwf in libexpat before 2.8.2 has an integer overflow in endDoctypeDecl via NOTATION declarations.0.1%
CVE-2026-56410Medium 6.9xmlwf in libexpat before 2.8.2 has an integer overflow in resolveSystemId.0.1%
CVE-2026-56409Medium 6.5xmlwf in libexpat before 2.8.2 has an integer overflow for the output filename when -d outputDir is used.0.1%
CVE-2026-56408Medium 6.9libexpat before 2.8.2 has an integer overflow in copyString.0.1%
CVE-2026-56407Medium 6.9libexpat before 2.8.2 has an integer overflow in doProlog that is related to storeEntityValue and entity textLen.0.2%
CVE-2026-56406Medium 6.9libexpat before 2.8.2 has an integer overflow in XML_ParseBuffer because it lacked a check that was present in XML_Parse.0.2%
CVE-2026-56405Medium 6.9libexpat before 2.8.2 has an integer overflow in getAttributeId.0.1%
CVE-2026-56404Medium 6.9libexpat before 2.8.2 has an integer overflow in addBinding.0.1%
CVE-2026-56403Medium 6.9libexpat before 2.8.2 has an integer overflow in storeAtts.0.2%
CVE-2026-56132Medium 6.9In libexpat before 2.8.2, there is a heap-based buffer overflow in doProlog in xmlparse.c because scaffold backing array reallocation is mishandled when there is data-structure sharing across parsers.0.1%
CVE-2026-56131Medium 4.9libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_ResumeParser from within handlers in cases of a policy violation. Thus, a use-after-free can occur (similar to the CVE-2026-5020.2%
CVE-2026-50219Medium 4.9libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_GetBuffer, XML_Parse, XML_ParseBuffer, XML_ParserFree, or XML_ParserReset from within handlers in cases of a policy violation. 0.2%
CVE-2026-45186Low 2.9In libexpat before 2.8.1, the computational complexity of attribute name collision checks allows a denial of service via moderately sized crafted XML input.0.5%
CVE-2026-41080Low 2.9libexpat before 2.8.0 uses insufficient entropy, and thus hash flooding can occur via a crafted XML document.0.4%
CVE-2026-32778Low 2.9libexpat before 2.7.5 allows a NULL pointer dereference in the function setContext on retry after an earlier ouf-of-memory condition.0.2%
CVE-2026-32777Medium 4.0libexpat before 2.7.5 allows an infinite loop while parsing DTD content.0.2%
CVE-2026-32776Medium 4.0libexpat before 2.7.5 allows a NULL pointer dereference with empty external parameter entity content.0.2%
CVE-2026-25210Medium 6.9In libexpat before 2.7.4, the doContent function does not properly determine the buffer size bufSize because there is no integer overflow check for tag buffer reallocation.0.2%
CVE-2026-24515Low 2.9In libexpat before 2.7.4, XML_ExternalEntityParserCreate does not copy unknown encoding handler user data.0.2%
CVE-2025-66382Low 2.9In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time.0.2%
CVE-2025-59375High 7.5libexpat in Expat before 2.7.2 allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing.1.4%