Libexpat Project
Vulnerability activity for Libexpat Project: what is being exploited, what was published lately, and when the next patch release is due.
Last 30 days
- CVEs
- 0
- Critical (CVSS 9+)
- 0
- Exploited (CISA KEV)
- 0
- With exploit code
- 0
Last 90 days
- CVEs
- 3
- Critical (CVSS 9+)
- 0
- Exploited (CISA KEV)
- 0
- With exploit code
- 0
Last 365 days
- CVEs
- 24
- Critical (CVSS 9+)
- 0
- Exploited (CISA KEV)
- 0
- With exploit code
- 0
Exploited now
None of this vendor's CVEs are on CISA's known-exploited list.
Recent
- 4.9MediumAug 20, 2026libexpat Memory corruptionCVE-2026-76957libexpat 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.
- 5.9MediumAug 20, 2026libexpat Denial of serviceCVE-2026-76956In 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 service via crafted XML content.
- 7.5HighAug 18, 2026libexpat Denial of serviceCVE-2026-66046Expat through 2.8.3 contains a denial of service vulnerability caused by quadratic algorithmic complexity in the storeAtts() function in xmlparse.c, where processing N specified attributes with non-normalized values triggers an O(N^2) linear scan of elementType->defaultAtts to determine CDATA status. A remote unauthenticated attacker can supply a single well-formed XML document of a few megabytes to an application parsing untrusted XML to cause excessive CPU consumption, resulting in denial of s
- 4.9MediumJun 21, 2026libexpat Memory corruptionCVE-2026-56412libexpat 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 use-after-free can occur. NOTE: this issue exists because of an incomplete fix for CVE-2026-50219.
- 6.9MediumJun 21, 2026libexpat Memory corruptionCVE-2026-56411xmlwf in libexpat before 2.8.2 has an integer overflow in endDoctypeDecl via NOTATION declarations.
- 6.9MediumJun 21, 2026libexpat Memory corruptionCVE-2026-56410xmlwf in libexpat before 2.8.2 has an integer overflow in resolveSystemId.
- 6.5MediumJun 21, 2026libexpat Memory corruptionCVE-2026-56409xmlwf in libexpat before 2.8.2 has an integer overflow for the output filename when -d outputDir is used.
- 6.9MediumJun 21, 2026libexpat Memory corruptionCVE-2026-56408libexpat before 2.8.2 has an integer overflow in copyString.
- 6.9MediumJun 21, 2026libexpat Memory corruptionCVE-2026-56407libexpat before 2.8.2 has an integer overflow in doProlog that is related to storeEntityValue and entity textLen.
- 6.9MediumJun 21, 2026libexpat Memory corruptionCVE-2026-56406libexpat before 2.8.2 has an integer overflow in XML_ParseBuffer because it lacked a check that was present in XML_Parse.
- 6.9MediumJun 21, 2026libexpat Memory corruptionCVE-2026-56405libexpat before 2.8.2 has an integer overflow in getAttributeId.
- 6.9MediumJun 21, 2026libexpat Memory corruptionCVE-2026-56404libexpat before 2.8.2 has an integer overflow in addBinding.
- 6.9MediumJun 21, 2026libexpat Memory corruptionCVE-2026-56403libexpat before 2.8.2 has an integer overflow in storeAtts.
- 6.9MediumJun 19, 2026libexpat Memory corruptionCVE-2026-56132In 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.
- 4.9MediumJun 19, 2026libexpat Memory corruptionCVE-2026-56131libexpat 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-50219 situation).
- 4.9MediumJun 4, 2026libexpat Memory corruptionCVE-2026-50219libexpat 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. Thus, a use-after-free can occur,
- 2.9LowMay 10, 2026libexpat Denial of serviceCVE-2026-45186In libexpat before 2.8.1, the computational complexity of attribute name collision checks allows a denial of service via moderately sized crafted XML input.
- 2.9LowApr 16, 2026libexpatCVE-2026-41080libexpat before 2.8.0 uses insufficient entropy, and thus hash flooding can occur via a crafted XML document.
- 2.9LowMar 16, 2026libexpat Memory corruptionCVE-2026-32778libexpat before 2.7.5 allows a NULL pointer dereference in the function setContext on retry after an earlier ouf-of-memory condition.
- 4.0MediumMar 16, 2026libexpat Denial of serviceCVE-2026-32777libexpat before 2.7.5 allows an infinite loop while parsing DTD content.
- 4.0MediumMar 16, 2026libexpat Memory corruptionCVE-2026-32776libexpat before 2.7.5 allows a NULL pointer dereference with empty external parameter entity content.
- 6.9MediumJan 30, 2026libexpat Memory corruptionCVE-2026-25210In 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.
- 2.9LowJan 23, 2026libexpat Memory corruptionCVE-2026-24515In libexpat before 2.7.4, XML_ExternalEntityParserCreate does not copy unknown encoding handler user data.
- 2.9LowNov 28, 2025libexpatCVE-2025-66382In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time.
Top products
- libexpat24 CVEs in the last year
Counts cover CVEs and advisories Watch Floor tracks, by the date they became news. Updated every 10 minutes.