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.

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.

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 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)

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 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)

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 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)

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)

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)

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 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)

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)

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)

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 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)

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 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)

The libxml2 library is a development toolbox providing the implementation of various XML standards.

Security Fix(es):

• libxml2: Stack Buffer Overflow in xmllint Interactive Shell Command Handling (CVE-2025-6170)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The libxml2 library is a development toolbox providing the implementation of various XML standards.

Security Fix(es):

• libxml2: Stack Buffer Overflow in xmllint Interactive Shell Command Handling (CVE-2025-6170)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The libxml2 library is a development toolbox providing the implementation of various XML standards.

Security Fix(es):

• libxml2: Stack Buffer Overflow in xmllint Interactive Shell Command Handling (CVE-2025-6170)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

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.

The libxml2 library is a development toolbox providing the implementation of various XML standards.

Security Fix(es):

• libxml2: Stack Buffer Overflow in xmllint Interactive Shell Command Handling (CVE-2025-6170)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The libxml2 library is a development toolbox providing the implementation of various XML standards.

Security Fix(es):

• libxml2: Stack Buffer Overflow in xmllint Interactive Shell Command Handling (CVE-2025-6170)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The libxml2 library is a development toolbox providing the implementation of various XML standards.

Security Fix(es):

• libxml2: Stack Buffer Overflow in xmllint Interactive Shell Command Handling (CVE-2025-6170)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

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.

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-2023-45322: fix use-after-free in xmlStaticCopyNodeList when copying DTDs
• CVE-2024-34459: fix buffer over-read in xmlHTMLPrintFileContext in xmllint
• CVE-2025-6170: fix potential buffer overflows in xmllint interactive shell
• CVE-2025-8732: fix stack overflow from self-referencing SGML CATALOG entries
• CVE-2026-0989: add RelaxNG include recursion limit
• CVE-2026-0990: prevent infinite recursion in xmlCatalogListXMLResolveURI
• CVE-2026-0992: ignore repeated nextCatalog entries in XML catalog parsing
• CVE-2026-1757: fix memory leak in xmllint interactive shell

• CVE-2025-6170: fix potential buffer overflows in xmllint interactive shell

Heap use after free (UAF) leads to Denial of service (DoS). (CVE-2025-49794) Null pointer dereference leads to Denial of service (DoS). (CVE-2025-49795) Type confusion leads to Denial of service (DoS). (CVE-2025-49796) Integer Overflow Leading to Buffer Overflow in xmlBuildQName(). (CVE-2025-6021) Stack-based Buffer Overflow in xmllint Shell. (CVE-2025-6170) Type confusion in xmlNode.psvi between stylesheet and source nodes. (CVE-2025-7424) Heap-use-after-free in xmlFreeID caused by atype corruption. (CVE-2025-7425)

These are all security issues fixed in the libxml2-2-2.13.8-2.1 package on the GA media of openSUSE Tumbleweed.

This update for libxml2 fixes the following issues:

• CVE-2025-49794: Fixed a heap use after free which could lead to denial of service. (bsc#1244554)
• CVE-2025-49796: Fixed type confusion which could lead to denial of service. (bsc#1244557)
• CVE-2025-49795: Fixed a null pointer dereference which could lead to denial of service. (bsc#1244555)
• CVE-2025-6170: Fixed a stack buffer overflow which could lead to a crash. (bsc#1244700)
• CVE-2025-6021: Fixed an integer overflow in xmlBuildQName() which could lead to stack buffer overflow. (bsc#1244590)

This update for libxml2 fixes the following issues:

• CVE-2025-49794: Fixed a heap use after free which could lead to denial of service. (bsc#1244554)
• CVE-2025-49796: Fixed type confusion which could lead to denial of service. (bsc#1244557)
• CVE-2025-6170: Fixed a stack buffer overflow which could lead to a crash. (bsc#1244700)
• CVE-2025-6021: Fixed an integer overflow in xmlBuildQName() which could lead to stack buffer overflow. (bsc#1244590)

This update for libxml2 fixes the following issues:

• CVE-2025-49794: Fixed a heap use after free which could lead to denial of service. (bsc#1244554)
• CVE-2025-49796: Fixed type confusion which could lead to denial of service. (bsc#1244557)
• CVE-2025-6170: Fixed a stack buffer overflow which could lead to a crash. (bsc#1244700)
• CVE-2025-6021: Fixed an integer overflow in xmlBuildQName() which could lead to stack buffer overflow. (bsc#1244590)

This update for libxml2 fixes the following issues:

• CVE-2025-49794: Fixed a heap use after free which could lead to denial of service. (bsc#1244554)
• CVE-2025-49796: Fixed type confusion which could lead to denial of service. (bsc#1244557)
• CVE-2025-49795: Fixed a null pointer dereference which could lead to denial of service. (bsc#1244555)
• CVE-2025-6170: Fixed a stack buffer overflow which could lead to a crash. (bsc#1244700)
• CVE-2025-6021: Fixed an integer overflow in xmlBuildQName() which could lead to stack buffer overflow. (bsc#1244590)

This update for libxml2 fixes the following issues:

• CVE-2025-49794: Fixed a heap use after free which could lead to denial of service. (bsc#1244554)
• CVE-2025-49796: Fixed type confusion which could lead to denial of service. (bsc#1244557)
• CVE-2025-6170: Fixed a stack buffer overflow which could lead to a crash. (bsc#1244700)
• CVE-2025-6021: Fixed an integer overflow in xmlBuildQName() which could lead to stack buffer overflow. (bsc#1244590)

This update for libxml2 fixes the following issues:

• CVE-2025-6021: Integer Overflow in xmlBuildQName() Leads to Stack Buffer Overflow in libxml2 [bsc#1244580]
• CVE-2025-6170: stack buffer overflow may lead to a crash [bsc#1244700]
• CVE-2025-7425: Heap Use-After-Free in libxslt caused by atype corruption in xmlAttrPtr [bsc#1246296]
• CVE-2025-49794: heap use after free (UAF) can lead to Denial of service (DoS) [bsc#1244554]
• CVE-2025-49795: null pointer dereference may lead to Denial of service (DoS) [bsc#1244555]
• CVE-2025-49796: type confusion may lead to Denial of service (DoS) [bsc#1244557]

This update for libxml2 fixes the following issues:

• CVE-2025-6021: Integer Overflow in xmlBuildQName() Leads to Stack Buffer Overflow in libxml2 [bsc#1244580]
• CVE-2025-6170: stack buffer overflow may lead to a crash [bsc#1244700]
• CVE-2025-7425: Heap Use-After-Free in libxslt caused by atype corruption in xmlAttrPtr [bsc#1246296]
• CVE-2025-49794: heap use after free (UAF) can lead to Denial of service (DoS) [bsc#1244554]
• CVE-2025-49795: null pointer dereference may lead to Denial of service (DoS) [bsc#1244555]
• CVE-2025-49796: type confusion may lead to Denial of service (DoS) [bsc#1244557]

Ahmed Lekssays discovered that libxml2 did not properly perform certain mathematical operations, leading to an integer overflow. An attacker could possibly use this issue to cause a crash, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2025-6021)

Ahmed Lekssays discovered that libxml2 did not properly validate the size of an untrusted input stream. An attacker could possibly use this issue to cause a crash, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2025-6170)

Nikita Sveshnikov discovered that libxml2 did not properly handle certain XPath expressions, leading to a use-after-free vulnerability. An attacker could potentially exploit this issue to cause a denial of service. (CVE-2025-49794)

Nikita Sveshnikov discovered that libxml2 contained a type confusion vulnerability when parsing specially crafted XML documents. An attacker could potentially exploit this issue to cause a denial of service. (CVE-2025-49796)