Recherche « libexpat project libexpat »
18 CVE
-
CVE-2026-76957 7.8 Élevée
libexpat project libexpat
libexpat 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.
-
CVE-2026-76956 7.5 Élevée
libexpat project libexpat
In 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.
-
CVE-2026-66046 7.5 Élevée
libexpat project libexpat
Expat 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 service without requiring authentication, external entity resolution, or non-default parser options.
-
CVE-2026-72522 6.2 Moyenne
libexpat project libexpat
libexpat 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.
-
CVE-2026-56412 5.9 Moyenne
libexpat project libexpat
libexpat 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.
-
CVE-2026-56411 6.9 Moyenne
libexpat project libexpat
xmlwf in libexpat before 2.8.2 has an integer overflow in endDoctypeDecl via NOTATION declarations.
-
CVE-2026-56410 6.9 Moyenne
libexpat project libexpat
xmlwf in libexpat before 2.8.2 has an integer overflow in resolveSystemId.
-
CVE-2026-56409 6.5 Moyenne
libexpat project libexpat
xmlwf in libexpat before 2.8.2 has an integer overflow for the output filename when -d outputDir is used.
-
CVE-2026-56408 6.9 Moyenne
libexpat project libexpat
libexpat before 2.8.2 has an integer overflow in copyString.
-
CVE-2026-56407 6.9 Moyenne
libexpat project libexpat
libexpat before 2.8.2 has an integer overflow in doProlog that is related to storeEntityValue and entity textLen.
-
CVE-2026-56406 6.9 Moyenne
libexpat project libexpat
libexpat before 2.8.2 has an integer overflow in XML_ParseBuffer because it lacked a check that was present in XML_Parse.
-
CVE-2026-56405 6.9 Moyenne
libexpat project libexpat
libexpat before 2.8.2 has an integer overflow in getAttributeId.
-
CVE-2026-56404 6.9 Moyenne
libexpat project libexpat
libexpat before 2.8.2 has an integer overflow in addBinding.
-
CVE-2026-56403 6.9 Moyenne
libexpat project libexpat
libexpat before 2.8.2 has an integer overflow in storeAtts.
-
CVE-2026-56132 6.9 Moyenne
libexpat project libexpat
In 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.
-
CVE-2026-56131 4.9 Moyenne
libexpat project libexpat
libexpat 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).
-
CVE-2026-50219 5.9 Moyenne
libexpat project libexpat
libexpat 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,
-
CVE-2026-45186 7.5 Élevée
libexpat project libexpat · Red Hat Enterprise Linux 10 · Red Hat Enterprise Linux 8 · Red Hat Enterprise Linux 9
In libexpat before 2.8.1, the computational complexity of attribute name collision checks allows a denial of service via moderately sized crafted XML input.