Search for packages
| purl | pkg:deb/debian/libxml2@2.9.4%2Bdfsg1-7%2Bdeb10u4 |
| Next non-vulnerable version | 2.15.1+dfsg-2 |
| Latest non-vulnerable version | 2.15.1+dfsg-2 |
| Risk | 4.1 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-27jd-t23h-73f4
Aliases: CVE-2025-6021 |
libxml2: Integer Overflow in xmlBuildQName() Leads to Stack Buffer Overflow in libxml2 |
Affected by 4 other vulnerabilities. |
|
VCID-31w8-13b6-8beh
Aliases: CVE-2025-24928 |
libxml2: Stack-based buffer overflow in xmlSnprintfElements of libxml2 |
Affected by 4 other vulnerabilities. |
|
VCID-464a-typa-7qbu
Aliases: CVE-2025-6170 |
libxml2: Stack Buffer Overflow in xmllint Interactive Shell Command Handling |
Affected by 4 other vulnerabilities. |
|
VCID-4m3j-qy8c-4uhk
Aliases: CVE-2022-2309 GHSA-wrxv-2j5q-m38w PYSEC-2022-230 |
NULL Pointer Dereference allows attackers to cause a denial of service (or application crash). This only applies when lxml is used together with libxml2 2.9.10 through 2.9.14. libxml2 2.9.9 and earlier are not affected. It allows triggering crashes through forged input data, given a vulnerable code sequence in the application. The vulnerability is caused by the iterwalk function (also used by the canonicalize function). Such code shouldn't be in wide-spread use, given that parsing + iterwalk would usually be replaced with the more efficient iterparse function. However, an XML converter that serialises to C14N would also be vulnerable, for example, and there are legitimate use cases for this code sequence. If untrusted input is received (also remotely) and processed via iterwalk function, a crash can be triggered. |
Affected by 4 other vulnerabilities. |
|
VCID-74y5-vcxn-2ygr
Aliases: CVE-2025-49794 |
libxml: Heap use after free (UAF) leads to Denial of service (DoS) |
Affected by 4 other vulnerabilities. |
|
VCID-782a-uast-nbch
Aliases: CVE-2019-20388 |
Multiple vulnerabilities have been found in libxml2, the worst of which could result in a Denial of Service condition. |
Affected by 21 other vulnerabilities. |
|
VCID-7bpp-2hvk-2udv
Aliases: CVE-2020-24977 |
Multiple vulnerabilities have been found in libxml2, the worst of which could result in a Denial of Service condition. |
Affected by 21 other vulnerabilities. |
|
VCID-8d2w-3c3p-zqaz
Aliases: CVE-2024-34459 |
libxml2: buffer over-read in xmlHTMLPrintFileContext in xmllint.c |
Affected by 4 other vulnerabilities. |
|
VCID-9hqf-12yh-bkc8
Aliases: CVE-2021-3518 GHSA-v4f8-2847-rwm7 |
Multiple vulnerabilities have been found in libxml2, the worst of which could result in a Denial of Service condition. |
Affected by 21 other vulnerabilities. |
|
VCID-aasn-u7fd-8bhy
Aliases: CVE-2023-39615 |
Improper Restriction of Operations within the Bounds of a Memory Buffer Xmlsoft Libxml2 v2.11.0 was discovered to contain a global buffer overflow via the xmlSAX2StartElement() function at /libxml2/SAX2.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via supplying a crafted XML file. |
Affected by 4 other vulnerabilities. |
|
VCID-ahha-vnq4-7qd2
Aliases: CVE-2025-9714 |
libxslt: libxml2: Inifinite recursion at exsltDynMapFunction function in libexslt/dynamic.c |
Affected by 4 other vulnerabilities. |
|
VCID-azzy-m5pc-qudn
Aliases: CVE-2017-16932 GHSA-x2fm-93ww-ggvx |
Loop with Unreachable Exit Condition ('Infinite Loop') parser.c in libxml2 does not prevent infinite recursion in parameter entities. |
Affected by 21 other vulnerabilities. |
|
VCID-bejh-22y7-kuh6
Aliases: CVE-2018-14404 GHSA-6qvp-r6r3-9p7h |
NULL Pointer Dereference A NULL pointer dereference vulnerability exists in the xpath.c:xmlXPathCompOpEval() function of libxml2 when parsing an invalid XPath expression in the XPATH_OP_AND or XPATH_OP_OR case. Applications processing untrusted XSL format inputs with the use of the libxml2 library may be vulnerable to a denial of service attack due to a crash of the application. |
Affected by 21 other vulnerabilities. |
|
VCID-bz1e-1ypb-kkgg
Aliases: CVE-2025-49796 |
libxml: Type confusion leads to Denial of service (DoS) |
Affected by 4 other vulnerabilities. |
|
VCID-c9ds-faa9-t7be
Aliases: CVE-2024-56171 |
libxml2: Use-After-Free in libxml2 |
Affected by 4 other vulnerabilities. |
|
VCID-cbm2-cez4-bqgh
Aliases: CVE-2022-23308 |
Use After Free `valid.c` in libxml2 before 2.9.13 has a use-after-free of `ID` and `IDREF` attributes. |
Affected by 21 other vulnerabilities. |
|
VCID-d68t-f8j1-h3am
Aliases: CVE-2024-25062 |
Use After Free When using the XML Reader interface with DTD validation and XInclude expansion enabled, processing crafted XML documents can lead to an xmlValidatePopElement use-after-free. |
Affected by 4 other vulnerabilities. |
|
VCID-drkd-yykc-ayge
Aliases: CVE-2025-32414 |
libxml2: Out-of-Bounds Read in libxml2 |
Affected by 4 other vulnerabilities. |
|
VCID-eb6k-ppfd-m7a3
Aliases: CVE-2022-40304 |
Multiple vulnerabilities have been found in libxml2, the worst of which could result in arbitrary code execution. |
Affected by 21 other vulnerabilities. |
|
VCID-ek5d-m9pn-3fec
Aliases: CVE-2021-3517 GHSA-jw9f-hh49-cvp9 |
Multiple vulnerabilities have been found in libxml2, the worst of which could result in a Denial of Service condition. |
Affected by 21 other vulnerabilities. |
|
VCID-hafa-bcpu-8uaj
Aliases: CVE-2025-27113 |
libxml2: NULL Pointer Dereference in libxml2 xmlPatMatch |
Affected by 4 other vulnerabilities. |
|
VCID-nuh8-qd25-ykan
Aliases: CVE-2016-3709 |
libxml2: Incorrect server side include parsing can lead to XSS |
Affected by 4 other vulnerabilities. |
|
VCID-pdv9-xrh8-d3fz
Aliases: CVE-2023-45322 |
Use After Free This advisory has been marked as False Positive and removed. |
Affected by 4 other vulnerabilities. |
|
VCID-qh44-gavt-rbdw
Aliases: CVE-2022-49043 |
libxml: use-after-free in xmlXIncludeAddNode |
Affected by 4 other vulnerabilities. |
|
VCID-qp6y-dt1j-97df
Aliases: CVE-2025-32415 |
libxml2: Out-of-bounds Read in xmlSchemaIDCFillNodeTables |
Affected by 4 other vulnerabilities. |
|
VCID-qpnt-xvgv-s3cq
Aliases: CVE-2023-28484 |
This advisory has been invalidated. |
Affected by 21 other vulnerabilities. |
|
VCID-qtp3-a1g7-8kgw
Aliases: CVE-2016-9318 |
Improper Restriction of XML External Entity Reference libxml2, as used in XMLSec and other products, does not offer a flag directly indicating that the current document may be read but other files may not be opened, which makes it easier for remote attackers to conduct XML External Entity (XXE) attacks via a crafted document. |
Affected by 21 other vulnerabilities. |
|
VCID-qv3r-ppuc-zycz
Aliases: CVE-2020-7595 GHSA-7553-jr98-vx47 |
libxml as used in Nokogiri has an infinite loop in a certain end-of-file situation xmlStringLenDecodeEntities in parser.c in libxml2 2.9.10 has an infinite loop in a certain end-of-file situation. The Nokogiri RubyGem has patched its vendored copy of libxml2 in order to prevent this issue from affecting nokogiri. |
Affected by 21 other vulnerabilities. |
|
VCID-rsvx-3f49-v3an
Aliases: CVE-2021-3541 |
Improper Restriction of Recursive Entity References in DTDs (XML Entity Expansion) A flaw was found in libxml2. By exploiting an exponential entity expansion attack its possible bypassing all existing protection mechanisms and lead to a denial of service. |
Affected by 21 other vulnerabilities. |
|
VCID-s9r4-a3uz-4yhp
Aliases: CVE-2022-29824 |
Integer Overflow or Wraparound In libxml2 before 2.9.14, several buffer handling functions in buf.c (xmlBuf*) and tree.c (xmlBuffer*) don't check for integer overflows. This can result in out-of-bounds memory writes. Exploitation requires a victim to open a crafted, multi-gigabyte XML file. Other software using libxml2's buffer functions, for example libxslt through 1.1.35, is affected as well. |
Affected by 21 other vulnerabilities. |
|
VCID-t53m-6vvr-27cf
Aliases: CVE-2018-14567 |
Loop with Unreachable Exit Condition ('Infinite Loop') libxml2, if --with-lzma is used, allows remote attackers to cause a denial of service (infinite loop) via a crafted XML file that triggers LZMA_MEMLIMIT_ERROR, as demonstrated by xmllint, a different vulnerability than CVE-2015-8035 and CVE-2018-9251. |
Affected by 21 other vulnerabilities. |
|
VCID-udew-3gre-13hy
Aliases: CVE-2022-40303 |
Multiple vulnerabilities have been found in libxml2, the worst of which could result in arbitrary code execution. |
Affected by 21 other vulnerabilities. |
|
VCID-ugyh-dycm-3bc3
Aliases: CVE-2019-19956 |
libxml2: memory leak in xmlParseBalancedChunkMemoryRecover in parser.c |
Affected by 21 other vulnerabilities. |
|
VCID-vf7b-s3y3-sfhw
Aliases: CVE-2021-3537 GHSA-286v-pcf5-25rc |
Multiple vulnerabilities have been found in libxml2, the worst of which could result in a Denial of Service condition. |
Affected by 21 other vulnerabilities. |
|
VCID-wc4g-sxyq-ubcd
Aliases: CVE-2017-18258 GHSA-882p-jqgm-f45g |
Allocation of Resources Without Limits or Throttling The xz_head function in xzlib.c in libxml2 allows remote attackers to cause a denial of service (memory consumption) via a crafted LZMA file, because the decoder functionality does not restrict memory usage to what is required for a legitimate file. |
Affected by 21 other vulnerabilities. |
|
VCID-x9ej-7dcq-tub2
Aliases: CVE-2023-29469 |
Double Free An issue was discovered in libxml2 before 2.10.4. When hashing empty dict strings in a crafted XML document, xmlDictComputeFastKey in dict.c can produce non-deterministic values, leading to various logic and memory errors, such as a double free. This behavior occurs because there is an attempt to use the first byte of an empty string, and any value is possible (not solely the '\0' value). |
Affected by 21 other vulnerabilities. |
|
VCID-xps8-1a3r-wke6
Aliases: CVE-2021-3516 |
Multiple vulnerabilities have been found in libxml2, the worst of which could result in a Denial of Service condition. |
Affected by 21 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-3whx-6t3e-7beq | Multiple vulnerabilities have been found in libxml2, the worst of which could result in the execution of arbitrary code. |
CVE-2017-5969
|
| VCID-4hws-gtxr-3bge | Improper Restriction of Operations within the Bounds of a Memory Buffer Buffer overflow in libxml2 allows remote attackers to execute arbitrary code by leveraging an incorrect limit for port values when handling redirects. |
CVE-2017-7376
|
| VCID-57yv-ay7b-v7ev | Out-of-bounds Write An integer overflow in xmlmemory.c in libxml2, as used in Google Chrome and other products, allowed a remote attacker to potentially exploit heap corruption via a crafted XML file. |
CVE-2017-5130
|
| VCID-8tej-h12t-2fag | Improper Restriction of XML External Entity Reference A flaw in libxml2 allows remote XML entity inclusion with default parser flags (i.e., when the caller did not request entity substitution, DTD validation, external DTD subset loading, or default DTD attributes). Depending on the context, this may expose a higher-risk attack surface in libxml2 not usually reachable with default parser flags, and expose content from local files, HTTP, or FTP servers (which might be otherwise unreachable). |
CVE-2017-7375
|
| VCID-gvmn-4dtv-8qcj | Improper Restriction of Operations within the Bounds of a Memory Buffer parser.c in libxml2 mishandles parameter-entity references because the NEXTL macro calls the xmlParserHandlePEReference function in the case of a '%' character in a DTD name. |
CVE-2017-16931
|
| VCID-mm88-amve-quh6 | Out-of-bounds Read The htmlParseTryOrFinish function in HTMLparser.c in libxml2 allows attackers to cause a denial of service (buffer over-read) or information disclosure. |
CVE-2017-8872
|
| VCID-qqte-z1e6-xuh7 | Improper Restriction of Operations within the Bounds of a Memory Buffer A buffer overflow was discovered in libxml2 . The function xmlSnprintfElementContent in valid.c is supposed to recursively dump the element content definition into a char buffer 'buf' of size 'size'. The variable len is assigned strlen(buf). If the content->type is XML_ELEMENT_CONTENT_ELEMENT, then (i) the content->prefix is appended to buf (if it actually fits) whereupon (ii) content->name is written to the buffer. However, the check for whether the content->name actually fits also uses 'len' rather than the updated buffer length strlen(buf). This allows us to write about "size" many bytes beyond the allocated memory. This vulnerability causes programs that use libxml2, such as PHP, to crash. |
CVE-2017-9047
|
| VCID-qxwq-xwaw-nyak | Multiple vulnerabilities have been found in libxml2, the worst of which could result in the execution of arbitrary code. |
CVE-2017-0663
|
| VCID-rhgj-t5cp-wkbh | Improper Restriction of Operations within the Bounds of a Memory Buffer libxml2 is vulnerable to a stack-based buffer overflow. The function xmlSnprintfElementContent in valid.c is supposed to recursively dump the element content definition into a char buffer 'buf' of size 'size'. At the end of the routine, the function may strcat two more characters without checking whether the current strlen(buf) + 2 < size. This vulnerability causes programs that use libxml2, such as PHP, to crash. |
CVE-2017-9048
|
| VCID-s9r4-a3uz-4yhp | Integer Overflow or Wraparound In libxml2 before 2.9.14, several buffer handling functions in buf.c (xmlBuf*) and tree.c (xmlBuffer*) don't check for integer overflows. This can result in out-of-bounds memory writes. Exploitation requires a victim to open a crafted, multi-gigabyte XML file. Other software using libxml2's buffer functions, for example libxslt through 1.1.35, is affected as well. |
CVE-2022-29824
|
| VCID-tn87-vke6-kuf6 | Use After Free Use after free in libxml2, as used in Google Chrome and other products, allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. |
CVE-2017-15412
GHSA-r58r-74gx-6wx3 |
| VCID-ymhr-ads4-qqdp | Out-of-bounds Read libxml2 is vulnerable to a heap-based buffer over-read in the xmlDictComputeFastKey function in dict.c. This vulnerability causes programs that use libxml2, such as PHP, to crash. |
CVE-2017-9049
|
| VCID-zm21-2pqq-3ker | Out-of-bounds Read libxml2 is vulnerable to a heap-based buffer over-read in the xmlDictAddString function in dict.c. This vulnerability causes programs that use libxml2, such as PHP, to crash. This vulnerability exists because of an incomplete fix for CVE-2016-1839. |
CVE-2017-9050
GHSA-8c56-cpmw-89x7 |