Vulnerability database · updated every 15 minutes
New vulnerabilities in the software websites run.
CVEs and security advisories for WordPress, its plugins and themes, npm, PyPI and the servers behind websites, merged from NVD, the CVE Program, GitHub, OSV.dev and WPVulnerability, with CISA's list of the ones attackers exploit.
- Tracked
- 55,384
- Published in 7 days
- 1,885
- Critical in 30 days
- 489
- Actively exploited
- 542
Results for “libxml2”
125 vulnerabilities- High 7.8
CVE-2026-86144 · libxml2
In 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 it) a custom resource loader accesses the internet and triggers XML external entity injection, SSRF, or a denial of service (e.g., for an attacker-controlled internet resource that is intentionally…
Published 5 Sept 2026 · Fixed in 2.15.4 · NVD - High 7.3
CVE-2026-86143 · libxml2
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.
Published 5 Sept 2026 · Fixed in 2.15.4 · NVD - High 7.8
CVE-2026-86142 · libxml2
In libxml2 before 2.15.4, there is a heap-based buffer overflow in xmlXPtrEvalXPtrPart because of xmlXPtrEval xpointer length saturation.
Published 5 Sept 2026 · Fixed in 2.15.4 · NVD - Low 3.3
CVE-2026-86141 · libxml2
xmlregexp 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.
Published 5 Sept 2026 · Fixed in 2.15.4 · NVD - High 7.8
CVE-2026-86140 · libxml2
In libxml2 before 2.15.4, xmlSnprintfElements in valid.c has a strcat stack-based buffer overflow.
Published 5 Sept 2026 · Fixed in 2.15.4 · NVD - High 7.8
CVE-2026-86139 · libxml2
In libxml2 before 2.15.4, xmlURIEscapeStr in uri.c has an integer overflow.
Published 5 Sept 2026 · Fixed in 2.15.4 · NVD - High 7.8
CVE-2026-86138 · libxml2
In libxml2 before 2.15.4, xmlDictAddQString in dict.c has an integer overflow and resultant heap-based buffer overflow.
Published 5 Sept 2026 · Fixed in 2.15.4 · NVD - Medium 6.1
CVE-2026-86137 · libxml2
In libxml2 before 2.15.4, xmlFAParsePosCharGroup has an out-of-bounds read, aka an out-of-bounds read in the NXT macro in xmlregexp.
Published 5 Sept 2026 · Fixed in 2.15.4 · NVD - Low 1.8
CVE-2026-11979 · libxml2
libxml2 is vulnerable to multiple stack-based buffer overflows in the xmlcatalog utility when running in --shell mode. The usershell() function processes user input using fixed-size stack buffers without proper bounds checking. By supplying an overly long input line, an attacker can overflow internal buffers (command, arg, and argv) during input parsing. This results in memory corruption within…
Published 29 Jun 2026 · NVD - High 7.0
CVE-2026-6653 · libxml2
Use After Free in libxml2's xmlParseInternalSubset from GNOME libxml2 version 2.9.11 to 2.11.0 allows a remote attacker to cause a denial-of-service via maliciously crafted XML input with improper entity resolution handling.
Published 22 Jun 2026 · NVD - High 7.5
CVE-2026-6732 · libxml2
A flaw was found in libxml2. This vulnerability occurs when the library processes a specially crafted XML Schema Definition (XSD) validated document that includes an internal entity reference. An attacker could exploit this by providing a malicious document, leading to a type confusion error that causes the application to crash. This results in a denial of service (DoS), making the affected…
Published 23 Apr 2026 · Fixed in 2.15.3 · NVD - Low 2.9
CVE-2026-0992 · libxml2
A flaw was found in the libxml2 library. This uncontrolled resource consumption vulnerability occurs when processing XML catalogs that contain repeated <nextCatalog> elements pointing to the same downstream catalog. A remote attacker can exploit this by supplying crafted catalogs, causing the parser to redundantly traverse catalog chains. This leads to excessive CPU consumption and degrades…
Published 15 Jan 2026 · Fixed in 2.15.2 · NVD - Medium 5.9
CVE-2026-0990 · libxml2
A flaw was found in libxml2, an XML parsing library. This uncontrolled recursion vulnerability occurs in the xmlCatalogXMLResolveURI function when an XML catalog contains a delegate URI entry that references itself. A remote attacker could exploit this configuration-dependent issue by providing a specially crafted XML catalog, leading to infinite recursion and call stack exhaustion. This…
Published 15 Jan 2026 · Fixed in 2.15.2 · NVD - Low 3.7
CVE-2026-0989 · libxml2
A flaw was identified in the RelaxNG parser of libxml2 related to how external schema inclusions are handled. The parser does not enforce a limit on inclusion depth when resolving nested <include> directives. Specially crafted or overly complex schemas can cause excessive recursion during parsing. This may lead to stack exhaustion and application crashes, creating a denial-of-service risk.
Published 15 Jan 2026 · Fixed in 2.15.2 · NVD - Medium 5.5
CVE-2025-9714 · libxml2
Uncontrolled recursion in XPath evaluation in libxml2 up to and including version 2.9.14 allows a local attacker to cause a stack overflow via crafted expressions. XPath processing functions `xmlXPathRunEval`, `xmlXPathCtxtCompile`, and `xmlXPathEvalExpr` were resetting recursion depth to zero before making potentially recursive calls. When such functions were called recursively this could allow…
Published 10 Sept 2025 · Fixed in 2.10.0 · NVD - Low 1.9
CVE-2025-8732 · libxml2
A vulnerability was found in libxml2 up to 2.14.5. It has been declared as problematic. This vulnerability affects the function xmlParseSGMLCatalog of the component xmlcatalog. The manipulation leads to uncontrolled recursion. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment.…
Published 8 Aug 2025 · Fixed in 2.15.2 · NVD - High 7.5
CVE-2025-6021 · libxml2
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.
Published 12 Jun 2025 · Fixed in 2.14.4 · NVD - High 7.5
CVE-2025-32415 · libxml2
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.
Published 17 Apr 2025 · Fixed in 2.13.8, 2.14.2 · NVD - High 7.5
CVE-2025-32414 · libxml2
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.
Published 8 Apr 2025 · Fixed in 2.13.8, 2.14.2 · NVD - High 7.5
CVE-2025-27113 · libxml2
libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a NULL pointer dereference in xmlPatMatch in pattern.c.
Published 18 Feb 2025 · Fixed in 2.12.10, 2.13.6 · NVD - High 7.7
CVE-2025-24928 · libxml2
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.
Published 18 Feb 2025 · Fixed in 2.12.10, 2.13.6 · NVD - Critical 9.8
CVE-2024-56171 · libxml2
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.
Published 18 Feb 2025 · Fixed in 2.12.10, 2.13.6 · NVD - High 7.8
CVE-2022-49043 · libxml2
xmlXIncludeAddNode in xinclude.c in libxml2 before 2.11.0 has a use-after-free.
Published 26 Jan 2025 · Fixed in 2.11.0 · NVD - Critical 9.1
CVE-2024-40896 · libxml2
In libxml2 2.11 before 2.11.9, 2.12 before 2.12.9, and 2.13 before 2.13.3, the SAX parser can produce events for external entities even if custom SAX handlers try to override entity content (by setting "checked"). This makes classic XXE attacks possible.
Published 23 Dec 2024 · Fixed in 2.11.9, 2.12.9, 2.13.3 · NVD - High 7.5
CVE-2024-34459 · libxml2
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.
Published 14 May 2024 · Fixed in 2.11.8, 2.12.7 · NVD - High 7.5
CVE-2024-25062 · libxml2
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.
Published 4 Feb 2024 · Fixed in 2.11.7, 2.12.5 · NVD - Medium 6.5
CVE-2023-45322 · libxml2
libxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails. This occurs in xmlUnlinkNode in tree.c. NOTE: the vendor's position is "I don't think these issues are critical enough to warrant a CVE ID ... because an attacker typically can't control when memory allocations fail."
Published 6 Oct 2023 · NVD - Medium 6.5
CVE-2023-39615 · libxml2
Xmlsoft Libxml2 v2.11.0 was discovered to contain an out-of-bounds read 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. NOTE: the vendor's position is that the product does not support the legacy SAX1 interface with custom callbacks; there is a crash even without crafted input.
Published 29 Aug 2023 · NVD - Medium 6.5
CVE-2023-29469 · libxml2
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).
Published 24 Apr 2023 · Fixed in 2.10.4 · NVD - Medium 6.5
CVE-2023-28484 · libxml2
In libxml2 before 2.10.4, parsing of certain invalid XSD schemas can lead to a NULL pointer dereference and subsequently a segfault. This occurs in xmlSchemaFixupComplexType in xmlschemas.c.
Published 24 Apr 2023 · Fixed in 2.10.4 · NVD - High 7.8
CVE-2022-40304 · libxml2
An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be provoked.
Published 23 Nov 2022 · Fixed in 2.10.3 · NVD - High 7.5
CVE-2022-40303 · libxml2
An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to access an array at a negative 2GB offset, typically leading to a segmentation fault.
Published 23 Nov 2022 · Fixed in 2.10.3 · NVD - Medium 6.1
CVE-2016-3709 · libxml2
Possible cross-site scripting vulnerability in libxml after commit 960f0e2.
Published 28 Jul 2022 · Fixed in 2.9.11 · NVD - Medium 6.5
CVE-2022-29824 · libxml2
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.
Published 3 May 2022 · Fixed in 2.9.14 · NVD - High 7.5
CVE-2022-23308 · libxml2
valid.c in libxml2 before 2.9.13 has a use-after-free of ID and IDREF attributes.
Published 26 Feb 2022 · Fixed in 2.9.13 · NVD - Medium 6.5
CVE-2021-3596 · ImageMagick
A NULL pointer dereference flaw was found in ImageMagick in versions prior to 7.0.10-31 in ReadSVGImage() in coders/svg.c. This issue is due to not checking the return value from libxml2's xmlCreatePushParserCtxt() and uses the value directly, which leads to a crash and segmentation fault.
Published 24 Feb 2022 · Fixed in 7.0.10-31 · NVD - Medium 6.5
CVE-2021-3541 · libxml2
A flaw was found in libxml2. Exponential entity expansion attack its possible bypassing all existing protection mechanisms and leading to denial of service.
Published 9 Jul 2021 · Fixed in 2.9.11 · NVD - High 8.6
CVE-2021-3517 · Java, libxml2
There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11. An attacker who is able to supply a crafted file to be processed by an application linked with the affected functionality of libxml2 could trigger an out-of-bounds read. The most likely impact of this flaw is to application availability, with some potential impact to confidentiality and integrity if an…
Published 19 May 2021 · Fixed in 2.9.11 · NVD - High 8.8
CVE-2021-3518 · libxml2
There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact from this flaw is to confidentiality, integrity, and availability.
Published 18 May 2021 · Fixed in 2.9.11 · NVD - Medium 5.9
CVE-2021-3537 · Java, libxml2
A vulnerability found in libxml2 in versions before 2.9.11 shows that it did not propagate errors while parsing XML mixed content, causing a NULL dereference. If an untrusted XML document was parsed in recovery mode and post-validated, the flaw could be used to crash the application. The highest threat from this vulnerability is to system availability.
Published 14 May 2021 · Fixed in 2.9.11 · NVD - Critical 9.8
CVE-2019-8749 · Apple Safari
Multiple memory corruption issues were addressed with improved input validation. This issue is fixed in macOS Catalina 10.15, iOS 13, iCloud for Windows 7.14, iCloud for Windows 10.7, tvOS 13, macOS Catalina 10.15.1, Security Update 2019-001, and Security Update 2019-006, watchOS 6, iTunes 12.10.1 for Windows. Multiple issues in libxml2.
Published 27 Oct 2020 · Fixed in 13.0.1 · NVD - Medium 6.5
CVE-2020-24977 · libxml2
GNOME project libxml2 v2.9.10 has a global buffer over-read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c. The issue has been fixed in commit 50f06b3e.
Published 4 Sept 2020 · NVD - High 7.5
CVE-2020-7595 · libxml2
xmlStringLenDecodeEntities in parser.c in libxml2 2.9.10 has an infinite loop in a certain end-of-file situation.
Published 21 Jan 2020 · NVD - High 7.5
CVE-2019-20388 · libxml2
xmlSchemaPreRun in xmlschemas.c in libxml2 2.9.10 allows an xmlSchemaValidateStream memory leak.
Published 21 Jan 2020 · NVD - High 7.5
CVE-2019-19956 · libxml2
xmlParseBalancedChunkMemoryRecover in parser.c in libxml2 before 2.9.10 has a memory leak related to newDoc->oldNs.
Published 24 Dec 2019 · Fixed in 2.9.10 · NVD - High 7.5
CVE-2010-4657 · PHP
PHP5 before 5.4.4 allows passing invalid utf-8 strings via the xmlTextWriterWriteAttribute, which are then misparsed by libxml2. This results in memory leak into the resulting output.
Published 13 Nov 2019 · Fixed in 5.4.4 · NVD - Medium 6.5
CVE-2019-18853 · ImageMagick
ImageMagick before 7.0.9-0 allows remote attackers to cause a denial of service because XML_PARSE_HUGE is not properly restricted in coders/svg.c, related to SVG and libxml2.
Published 11 Nov 2019 · Fixed in 7.0.9-0 · NVD - High 8.8
CVE-2017-15412 · Google Chrome, libxml2
Use after free in libxml2 before 2.9.5, as used in Google Chrome prior to 63.0.3239.84 and other products, allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Published 28 Aug 2018 · Fixed in 2.9.5, 63.0.3239.84 · NVD - Medium 6.5
CVE-2018-14567 · libxml2
libxml2 2.9.8, 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.
Published 16 Aug 2018 · NVD - Medium 6.5
CVE-2016-9598 · libxml2
libxml2, as used in Red Hat JBoss Core Services, allows context-dependent attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted XML document. NOTE: this vulnerability exists because of a missing fix for CVE-2016-4483.
Published 16 Aug 2018 · Fixed in 2.9.4 · NVD
Where it comes from
The list holds every advisory UpHeron reads for the software it watches: WordPress and every plugin and theme its plugin reports, the packages in monitored repositories and manifests, and the servers and frameworks found on monitored websites. One vulnerability from several sources is one entry, under its CVE.
- NVD, the US National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- New and changed records of the CVE Program, read every 15 minutes, so a rating or fix added after a CVE is published reaches the list, and its alerts, within the hour. CVE content © 1999–2026 The MITRE Corporation, used under the CVE terms of use; CVE® is a registered trademark of The MITRE Corporation.
- OSV.dev, with the GitHub Advisory Database (CC BY 4.0).
- WPVulnerability (CC0) for WordPress plugins and themes, and WordPress's own security advisories.
- Node.js's own security release posts, read every 15 minutes, which name its vulnerabilities the day they are fixed, days before their CVE records.
- The security advisories projects publish on GitHub, and the CVEs libraries such as Brotli name in their release notes, which also count for the runtimes that bundle them.
- CISA's Known Exploited Vulnerabilities catalog.
Each day's new ones, grouped, and every critical one as soon as we find it: on the blog.
Run WordPress? The UpHeron plugin alerts you the day one of these affects your own site.