libxml2 security update
This library allows to manipulate XML files. It includes support to read, modify and write XML and HTML files. There is DTDs support this includes parsing and validation even with complex DtDs, either at parse time or later once the document has been modified. The output can be a simple SAX stream or and in-memory DOM like representations. In this case one can use the built-in XPath and XPointer implementation to select sub nodes or ranges. A flexible Input/Output mechanism is available, with existing HTTP and FTP modules and combined to an URI library. Security Fix(es): A flaw was found in libxml2. A local user or an attacker providing a specially crafted XML catalog can trigger a NULL pointer dereference during XML catalog parsing. This occurs when a `nextCatalog` element lacks its mandatory `catalog` attribute, leading to the application crashing and causing a Denial of Service (DoS).(CVE-2026-76781) In libxml2 before 2.15.4, there is a heap-based buffer overflow in xmlXPtrEvalXPtrPart because of xmlXPtrEval xpointer length saturation.(CVE-2026-86142) In 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 calling writecallback. This has security relevance for many types of uses of that length value within a callback.(CVE-2026-86143) In xinclude in libxml2 before 2.15.4, xmlXIncludeProcess and xmlXIncludeProcessTree do not propagate parseF
- Products
- libxml2
- Affected versions
- Not specified
- Fixed versions
- 2.9.14-35.oe2203sp4
- CVEs
- CVE-2026-76781, CVE-2026-86142, CVE-2026-86143, CVE-2026-86144
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 20:40 UTC · Revision 1
Source evidence
This library allows to manipulate XML files. It includes support to read, modify and write XML and HTML files. There is DTDs support this includes parsing and validation even with complex DtDs, either at parse time or later once the document has been modified. The output can be a simple SAX stream or and in-memory DOM like representations. In this case one can use the built-in XPath and XPointer implementation to select sub nodes or ranges. A flexible Input/Output mechanism is available, with existing HTTP and FTP modules and combined to an URI library. Security Fix(es): A flaw was found in libxml2. A local user or an attacker providing a specially crafted XML catalog can trigger a NULL pointer dereference during XML catalog parsing. This occurs when a `nextCatalog` element lacks its mandatory `catalog` attribute, leading to the application crashing and causing a Denial of Service (DoS).(CVE-2026-76781) In libxml2 before 2.15.4, there is a heap-based buffer overflow in xmlXPtrEvalXPtrPart because of xmlXPtrEval xpointer length saturation.(CVE-2026-86142) In 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 calling writecallback. This has security relevance for many types of uses of that length value within a callback.(CVE-2026-86143) In xinclude in libxml2 before 2.15.4, xmlXIncludeProcess and xmlXIncludeProcessTree do not propagate parseF
osv:OESA-2026-4373
libxml2
Fixed versions: 2.9.14-35.oe2203sp4
Complete source record
{
"id": "9905674c2f44f1679a70507081bc646d80a6413ba013320720cced52bad18a40",
"url": "https://osv.dev/vulnerability/OESA-2026-4373",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "libxml2 security update",
"summary": "This library allows to manipulate XML files. It includes support to read, modify and write XML and HTML files. There is DTDs support this includes parsing and validation even with complex DtDs, either at parse time or later once the document has been modified. The output can be a simple SAX stream or and in-memory DOM like representations. In this case one can use the built-in XPath and XPointer implementation to select sub nodes or ranges. A flexible Input/Output mechanism is available, with existing HTTP and FTP modules and combined to an URI library. Security Fix(es): A flaw was found in libxml2. A local user or an attacker providing a specially crafted XML catalog can trigger a NULL pointer dereference during XML catalog parsing. This occurs when a `nextCatalog` element lacks its mandatory `catalog` attribute, leading to the application crashing and causing a Denial of Service (DoS).(CVE-2026-76781) In libxml2 before 2.15.4, there is a heap-based buffer overflow in xmlXPtrEvalXPtrPart because of xmlXPtrEval xpointer length saturation.(CVE-2026-86142) In 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 calling writecallback. This has security relevance for many types of uses of that length value within a callback.(CVE-2026-86143) In xinclude in libxml2 before 2.15.4, xmlXIncludeProcess and xmlXIncludeProcessTree do not propagate parseF",
"evidence": "osv:OESA-2026-4373",
"products": [
{
"name": {
"value": "libxml2",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "2.9.14-35.oe2203sp4",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "OESA-2026-4373",
"aliases": [
"OESA-2026-4373"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "2.9.14-35.oe2203sp4"
}
]
}
],
"package": {
"name": "libxml2",
"purl": "pkg:rpm/openEuler/libxml2&distro=openEuler-22.03-LTS-SP4",
"ecosystem": "openEuler:22.03-LTS-SP4"
},
"database_specific": {
"source": "https://repo.openeuler.org/security/data/osv/OESA-2026-4373.json"
},
"ecosystem_specific": {
"src": [
"libxml2-2.9.14-35.oe2203sp4.src.rpm"
],
"noarch": [
"libxml2-help-2.9.14-35.oe2203sp4.noarch.rpm"
],
"x86_64": [
"libxml2-2.9.14-35.oe2203sp4.x86_64.rpm",
"libxml2-debuginfo-2.9.14-35.oe2203sp4.x86_64.rpm",
"libxml2-debugsource-2.9.14-35.oe2203sp4.x86_64.rpm",
"libxml2-devel-2.9.14-35.oe2203sp4.x86_64.rpm",
"python3-libxml2-2.9.14-35.oe2203sp4.x86_64.rpm"
],
"aarch64": [
"libxml2-2.9.14-35.oe2203sp4.aarch64.rpm",
"libxml2-debuginfo-2.9.14-35.oe2203sp4.aarch64.rpm",
"libxml2-debugsource-2.9.14-35.oe2203sp4.aarch64.rpm",
"libxml2-devel-2.9.14-35.oe2203sp4.aarch64.rpm",
"python3-libxml2-2.9.14-35.oe2203sp4.aarch64.rpm"
]
}
}
],
"modified": "2026-10-16T12:15:12.714797556Z",
"provider": "osv",
"upstream": [
"CVE-2026-76781",
"CVE-2026-86142",
"CVE-2026-86143",
"CVE-2026-86144"
],
"references": [
"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4373",
"https://nvd.nist.gov/vuln/detail/CVE-2026-76781",
"https://nvd.nist.gov/vuln/detail/CVE-2026-86142",
"https://nvd.nist.gov/vuln/detail/CVE-2026-86143",
"https://nvd.nist.gov/vuln/detail/CVE-2026-86144"
],
"provider_metadata": {
"severity": "Medium"
}
},
"related_cves": [
{
"value": "CVE-2026-76781",
"evidence": "/upstream"
},
{
"value": "CVE-2026-86142",
"evidence": "/upstream"
},
{
"value": "CVE-2026-86143",
"evidence": "/upstream"
},
{
"value": "CVE-2026-86144",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 340833,
"published_at": "2026-10-16T11:59:54+00:00"
}