Libxml2
133 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Libxml2, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
Libxml2 CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 1 |
| 2025-01 | 1 |
| 2025-02 | 3 |
| 2025-03 | 0 |
| 2025-04 | 2 |
| 2025-05 | 0 |
| 2025-06 | 5 |
| 2025-07 | 3 |
| 2025-08 | 1 |
| 2025-09 | 1 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 3 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 1 |
| 2026-05 | 8 |
| 2026-06 | 2 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 8 |
Severity
How the 133 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- Critical13
- High44
- Medium66
- Low9
Latest CVEs
The 15 most recently published vulnerabilities affecting Libxml2.
- CVE-2026-86144In xinclude in libxml2 before 2.15.4, xmlXIncludeProcess and xmlXIncludeProcessTree do not propagate parseFlags. This has security relevance for, for example, the XML_PARSE_NONET flag, if (without ...5.6
- CVE-2026-86143In xmlIO in libxml2 before 2.15.4, an inconsistency in xmlOutputWriteCallback and xmlBufUse causes negative lengths to reach write callbacks, aka a lack of a check for integer overflow before calli...6.9
- CVE-2026-86142In libxml2 before 2.15.4, there is a heap-based buffer overflow in xmlXPtrEvalXPtrPart because of xmlXPtrEval xpointer length saturation.6.9
- CVE-2026-86141xmlregexp in libxml2 before 2.15.4 has a NULL pointer dereference in xmlRegNewParserCtxt after a strdup failure, i.e., it does not calculate a string length after NULL checking.2.9
- CVE-2026-86140In libxml2 before 2.15.4, xmlSnprintfElements in valid.c has a strcat stack-based buffer overflow.8.0
- CVE-2026-86139In libxml2 before 2.15.4, xmlURIEscapeStr in uri.c has an integer overflow.6.9
- CVE-2026-86138In libxml2 before 2.15.4, xmlDictAddQString in dict.c has an integer overflow and resultant heap-based buffer overflow.6.9
- CVE-2026-86137In libxml2 before 2.15.4, xmlFAParsePosCharGroup has an out-of-bounds read, aka an out-of-bounds read in the NXT macro in xmlregexp.2.9
- CVE-2026-11979Stack-Based Buffer Overflow in libxml27.8
- CVE-2026-6653libxml2: Use after free in xmlParseInternalSubset via improper entity resolution handling—
- BDU:2026-06206Уязвимость функции xmlStringGetNodeList() компонента tree.c библиотеки Libxml2, связанная с ошибками разыменования указателя, позволяющая нарушителю вызвать отказ в обслуживании5.5
- BDU:2026-06203Уязвимость функции xmlBufSetInputBaseCur библиотеки Libxml2, позволяющая нарушителю вызвать отказ в обслуживании5.5
- BDU:2026-06202Уязвимость функции xmlMemStrdup() библиотеки Libxml2, позволяющая нарушителю вызвать отказ в обслуживании5.5
- BDU:2026-06208Уязвимость функции xmlFAParseQuantExact() компонента xmlregexp.c библиотеки Libxml2, позволяющая нарушителю вызвать отказ в обслуживании6.2
- BDU:2026-06207Уязвимость функции xmlBuildRelativeURI() компонента uri.c библиотеки Libxml2, позволяющая нарушителю вызвать отказ в обслуживании5.3
Product grouping is registry-driven, with AI assist and human review. How it works