Search for packages
| purl | pkg:deb/debian/libxml2@2.9.14%2Bdfsg-1.3~deb12u1 |
| Next non-vulnerable version | 2.9.14+dfsg-1.3~deb12u3 |
| Latest non-vulnerable version | 2.9.14+dfsg-1.3~deb12u3 |
| Risk | 4.1 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-3mkc-h7u6-6beh
Aliases: CVE-2025-49796 |
A vulnerability was found in libxml2. Processing certain sch:name elements from the input XML file can trigger a memory corruption issue. This flaw allows an attacker to craft a malicious XML input file that can lead libxml to crash, resulting in a denial of service or other possible undefined behavior due to sensitive data being corrupted in memory. |
Affected by 0 other vulnerabilities. |
|
VCID-3zy6-h7hv-1yhr
Aliases: CVE-2025-6021 |
A flaw was found in libxml2's xmlBuildQName function, where integer overflows in buffer size calculations can lead to a stack-based buffer overflow. This issue can result in memory corruption or a denial of service when processing crafted input. |
Affected by 0 other vulnerabilities. |
|
VCID-6h1b-etzt-juap
Aliases: CVE-2025-49794 |
A use-after-free vulnerability was found in libxml2. This issue occurs when parsing XPath elements under certain circumstances when the XML schematron has the <sch:name path="..."/> schema elements. This flaw allows a malicious actor to craft a malicious XML document used as input for libxml, resulting in the program's crash using libxml or other possible undefined behaviors. |
Affected by 0 other vulnerabilities. |
|
VCID-9r6n-66y4-3be2
Aliases: CVE-2025-6170 |
A flaw was found in the interactive shell of the xmllint command-line tool, used for parsing XML files. When a user inputs an overly long command, the program does not check the input size properly, which can cause it to crash. This issue might allow attackers to run harmful code in rare configurations without modern protections. |
Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-3mkc-h7u6-6beh | A vulnerability was found in libxml2. Processing certain sch:name elements from the input XML file can trigger a memory corruption issue. This flaw allows an attacker to craft a malicious XML input file that can lead libxml to crash, resulting in a denial of service or other possible undefined behavior due to sensitive data being corrupted in memory. |
CVE-2025-49796
|
| VCID-3zy6-h7hv-1yhr | A flaw was found in libxml2's xmlBuildQName function, where integer overflows in buffer size calculations can lead to a stack-based buffer overflow. This issue can result in memory corruption or a denial of service when processing crafted input. |
CVE-2025-6021
|
| VCID-6h1b-etzt-juap | A use-after-free vulnerability was found in libxml2. This issue occurs when parsing XPath elements under certain circumstances when the XML schematron has the <sch:name path="..."/> schema elements. This flaw allows a malicious actor to craft a malicious XML document used as input for libxml, resulting in the program's crash using libxml or other possible undefined behaviors. |
CVE-2025-49794
|
| VCID-6s1u-2xvj-vkbz | In libxml2 before 2.13.8 and 2.14.x before 2.14.2, xmlSchemaIDCFillNodeTables in xmlschemas.c has a heap-based buffer under-read. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be used. |
CVE-2025-32415
|
| VCID-9r6n-66y4-3be2 | A flaw was found in the interactive shell of the xmllint command-line tool, used for parsing XML files. When a user inputs an overly long command, the program does not check the input size properly, which can cause it to crash. This issue might allow attackers to run harmful code in rare configurations without modern protections. |
CVE-2025-6170
|
| VCID-9ym4-6av7-aqe3 | 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. |
CVE-2022-2309
GHSA-wrxv-2j5q-m38w PYSEC-2022-230 |
| VCID-bbv4-xhu4-5fhd | Use After Free This advisory has been marked as False Positive and removed. |
CVE-2023-45322
|
| VCID-bzfw-1axb-wqcc | xmlXIncludeAddNode in xinclude.c in libxml2 before 2.11.0 has a use-after-free. |
CVE-2022-49043
|
| VCID-d5gp-ggk5-mkh5 | 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. |
CVE-2023-39615
|
| VCID-e7ny-dgdx-wqhb | In libxml2 before 2.13.8 and 2.14.x before 2.14.2, out-of-bounds memory access can occur in the Python API (Python bindings) because of an incorrect return value. This occurs in xmlPythonFileRead and xmlPythonFileReadRaw because of a difference between bytes and characters. |
CVE-2025-32414
|
| VCID-fff8-g5p5-uba1 | libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free in xmlSchemaIDCFillNodeTables and xmlSchemaBubbleIDCNodeTables in xmlschemas.c. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be used. |
CVE-2024-56171
|
| VCID-h8dr-ab5d-e7f4 | libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a NULL pointer dereference in xmlPatMatch in pattern.c. |
CVE-2025-27113
|
| VCID-s24p-gfz1-d7cs | libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a stack-based buffer overflow in xmlSnprintfElements in valid.c. To exploit this, DTD validation must occur for an untrusted document or untrusted DTD. NOTE: this is similar to CVE-2017-9047. |
CVE-2025-24928
|
| VCID-uhs1-t4hc-jqdk | Possible cross-site scripting vulnerability in libxml after commit 960f0e2. |
CVE-2016-3709
|
| VCID-x4wq-q8ae-kff2 | An issue was discovered in libxml2 before 2.11.7 and 2.12.x before 2.12.5. 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. |
CVE-2024-25062
|
| VCID-zxp8-ej4m-cban | An issue was discovered in xmllint (from libxml2) before 2.11.8 and 2.12.x before 2.12.7. Formatting error messages with xmllint --htmlout can result in a buffer over-read in xmlHTMLPrintFileContext in xmllint.c. |
CVE-2024-34459
|