libxml2
xmlsoft- Product type
- Other
- Catalog vulnerabilities
- 115
Severity across 15 analyzed records
en
Verify to analyze this security profile
As of 09/13/2026, within CyStack's analyzed data, libxml2 has 9 security vulnerabilities published in the last 90 days. Of these, 1 is rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of libxml2 and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-86144 | Exploitation statusNot known exploited | FixYes | Published09/05/2026 | SeverityMedium |
CVE-2026-86143 | Exploitation statusNot known exploited | FixYes | Published09/05/2026 | SeverityMedium |
CVE-2026-86142 | Exploitation statusNot confirmed | FixYes | Published09/05/2026 | SeverityMedium |
CVE-2026-86141 | Exploitation statusNot known exploited | FixYes | Published09/05/2026 | SeverityLow |
CVE-2026-86140 | Exploitation statusNot known exploited | FixYes | Published09/05/2026 | SeverityHigh |
CVE-2026-86139 | Exploitation statusNot known exploited | FixYes | Published09/05/2026 | SeverityMedium |
CVE-2026-86138 | Exploitation statusNot known exploited | FixYes | Published09/05/2026 | SeverityMedium |
CVE-2026-86137 | Exploitation statusNot confirmed | FixYes | Published09/05/2026 | SeverityLow |
CVE-2026-11979Stack-Based Buffer Overflow in libxml2 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityLow |
CVE-2026-6653libxml2: Use after free in xmlParseInternalSubset via improper entity resolution handling | Exploitation statusNot known exploited | FixYes | Published06/22/2026 | SeverityHigh |
CVE-2026-6732Libxml2: libxml2: denial of service via crafted xsd-validated document | Exploitation statusNot known exploited | FixNot confirmed | Published04/23/2026 | SeverityMedium |
CVE-2026-0992Libxml2: libxml2: denial of service via crafted xml catalogs | Exploitation statusNot known exploited | FixNot confirmed | Published01/15/2026 | SeverityLow |
CVE-2026-0989Libxml2: unbounded relaxng include recursion leading to stack overflow | Exploitation statusNot known exploited | FixNot confirmed | Published01/15/2026 | SeverityLow |
CVE-2026-0990Libxml2: libxml2: denial of service via uncontrolled recursion in xml catalog processing | Exploitation statusNot known exploited | FixNot confirmed | Published01/15/2026 | SeverityMedium |
CVE-2025-9714Stack overflow in libxml2 | Exploitation statusNot known exploited | FixYes | Published09/10/2025 | SeverityMedium |
CVE-2025-8732libxml2 xmlcatalog xmlParseSGMLCatalog recursion | Exploitation statusPublic exploit | FixNot confirmed | Published08/08/2025 | SeverityMedium |
CVE-2025-6170Libxml2: stack buffer overflow in xmllint interactive shell command handling | Exploitation statusNot known exploited | FixYes | Published06/16/2025 | SeverityLow |
CVE-2025-6021Libxml2: integer overflow in xmlbuildqname() leads to stack buffer overflow in libxml2 | Exploitation statusPublic exploit | FixYes | Published06/12/2025 | SeverityHigh |
CVE-2025-32415 | Exploitation statusPublic exploit | FixYes | Published04/17/2025 | SeverityLow |
CVE-2025-32414 | Exploitation statusPublic exploit | FixYes | Published04/08/2025 | SeverityMedium |
CVE-2024-56171 | Exploitation statusNot known exploited | FixYes | Published02/18/2025 | SeverityHigh |
CVE-2025-24928 | Exploitation statusNot known exploited | FixYes | Published02/18/2025 | SeverityHigh |
CVE-2025-27113 | Exploitation statusNot known exploited | FixYes | Published02/18/2025 | SeverityLow |
CVE-2022-49043 | Exploitation statusNot known exploited | FixYes | Published01/26/2025 | SeverityHigh |
CVE-2024-40896 | Exploitation statusNot known exploited | FixYes | Published12/23/2024 | SeverityCritical |
CVE-2024-34459 | Exploitation statusPublic exploit | FixNot confirmed | Published05/13/2024 | SeverityHigh |
CVE-2024-25062 | Exploitation statusNot known exploited | FixNot confirmed | Published02/04/2024 | SeverityHigh |
CVE-2023-45322 | Exploitation statusNot known exploited | FixNot confirmed | Published10/06/2023 | SeverityUnknown |
CVE-2023-39615 | Exploitation statusPublic exploit | FixNot confirmed | Published08/29/2023 | SeverityUnknown |
CVE-2023-29469 | Exploitation statusNot known exploited | FixNot confirmed | Published04/24/2023 | SeverityMedium |
CVE-2023-28484 | Exploitation statusNot known exploited | FixNot confirmed | Published04/24/2023 | SeverityMedium |
CVE-2022-40304 | Exploitation statusNot known exploited | FixNot confirmed | Published11/23/2022 | SeverityHigh |
CVE-2022-40303 | Exploitation statusNot known exploited | FixNot confirmed | Published11/22/2022 | SeverityHigh |
CVE-2016-3709 | Exploitation statusNot confirmed | FixNot confirmed | Published07/28/2022 | SeverityUnknown |
CVE-2022-29824 | Exploitation statusNot confirmed | FixNot confirmed | Published05/03/2022 | SeverityUnknown |
CVE-2022-23308 | Exploitation statusNot known exploited | FixNot confirmed | Published02/26/2022 | SeverityHigh |
CVE-2021-3541 | Exploitation statusNot confirmed | FixNot confirmed | Published07/09/2021 | SeverityUnknown |
CVE-2021-3517 | Exploitation statusNot known exploited | FixNot confirmed | Published05/19/2021 | SeverityHigh |
CVE-2021-3518 | Exploitation statusNot confirmed | FixNot confirmed | Published05/18/2021 | SeverityUnknown |
CVE-2021-3537 | Exploitation statusNot confirmed | FixNot confirmed | Published05/14/2021 | SeverityUnknown |
CVE-2020-24977 | Exploitation statusNot confirmed | FixYes | Published09/03/2020 | SeverityUnknown |
CVE-2020-7595 | Exploitation statusPublic exploit | FixNot confirmed | Published01/21/2020 | SeverityHigh |
CVE-2019-20388 | Exploitation statusNot known exploited | FixNot confirmed | Published01/21/2020 | SeverityHigh |
CVE-2019-19956 | Exploitation statusNot known exploited | FixNot confirmed | Published12/24/2019 | SeverityHigh |
CVE-2017-15412 | Exploitation statusNot confirmed | FixNot confirmed | Published08/28/2018 | SeverityUnknown |
CVE-2018-14567 | Exploitation statusNot confirmed | FixNot confirmed | Published08/16/2018 | SeverityUnknown |
CVE-2016-9598 | Exploitation statusNot confirmed | FixNot confirmed | Published08/16/2018 | SeverityUnknown |
CVE-2016-9596 | Exploitation statusNot confirmed | FixNot confirmed | Published08/16/2018 | SeverityUnknown |
CVE-2016-9597 | Exploitation statusNot confirmed | FixNot confirmed | Published07/30/2018 | SeverityUnknown |
CVE-2018-14404 | Exploitation statusNot known exploited | FixNot confirmed | Published07/19/2018 | SeverityMedium |
CVE-2017-18258 | Exploitation statusNot confirmed | FixNot confirmed | Published04/08/2018 | SeverityUnknown |
CVE-2018-9251 | Exploitation statusNot confirmed | FixNot confirmed | Published04/04/2018 | SeverityUnknown |
CVE-2017-7375 | Exploitation statusNot known exploited | FixNot confirmed | Published02/19/2018 | SeverityCritical |
CVE-2017-7376 | Exploitation statusNot confirmed | FixNot confirmed | Published02/19/2018 | SeverityUnknown |
CVE-2017-5130 | Exploitation statusNot known exploited | FixNot confirmed | Published02/07/2018 | SeverityHigh |
CVE-2017-16932 | Exploitation statusNot known exploited | FixNot confirmed | Published11/23/2017 | SeverityHigh |
CVE-2017-16931 | Exploitation statusNot confirmed | FixNot confirmed | Published11/23/2017 | SeverityUnknown |
CVE-2017-9047 | Exploitation statusNot confirmed | FixNot confirmed | Published05/18/2017 | SeverityUnknown |
CVE-2017-9048 | Exploitation statusNot known exploited | FixNot confirmed | Published05/18/2017 | SeverityHigh |
CVE-2017-9050 | Exploitation statusNot known exploited | FixNot confirmed | Published05/18/2017 | SeverityHigh |
CVE-2017-9049 | Exploitation statusPublic exploit | FixNot confirmed | Published05/18/2017 | SeverityHigh |
CVE-2017-8872 | Exploitation statusNot known exploited | FixNot confirmed | Published05/10/2017 | SeverityCritical |
CVE-2016-4483 | Exploitation statusNot confirmed | FixNot confirmed | Published04/11/2017 | SeverityUnknown |
CVE-2017-5969 | Exploitation statusNot confirmed | FixNot confirmed | Published04/11/2017 | SeverityUnknown |
CVE-2016-9318 | Exploitation statusPublic exploit | FixNot confirmed | Published11/16/2016 | SeverityMedium |
CVE-2016-4658 | Exploitation statusNot confirmed | FixNot confirmed | Published09/25/2016 | SeverityUnknown |
CVE-2016-5131 | Exploitation statusNot known exploited | FixNot confirmed | Published07/23/2016 | SeverityHigh |
CVE-2016-4447 | Exploitation statusNot confirmed | FixNot confirmed | Published06/09/2016 | SeverityUnknown |
CVE-2016-4449 | Exploitation statusNot confirmed | FixNot confirmed | Published06/09/2016 | SeverityUnknown |
CVE-2016-4448 | Exploitation statusNot confirmed | FixNot confirmed | Published06/09/2016 | SeverityUnknown |
CVE-2016-1840 | Exploitation statusNot confirmed | FixNot confirmed | Published05/20/2016 | SeverityUnknown |
CVE-2016-1834 | Exploitation statusNot known exploited | FixNot confirmed | Published05/20/2016 | SeverityHigh |
CVE-2016-1839 | Exploitation statusNot confirmed | FixNot confirmed | Published05/20/2016 | SeverityUnknown |
CVE-2016-1838 | Exploitation statusNot confirmed | FixNot confirmed | Published05/20/2016 | SeverityUnknown |
CVE-2016-1836 | Exploitation statusNot confirmed | FixNot confirmed | Published05/20/2016 | SeverityUnknown |
CVE-2016-1833 | Exploitation statusNot confirmed | FixNot confirmed | Published05/20/2016 | SeverityUnknown |
CVE-2016-1837 | Exploitation statusNot confirmed | FixNot confirmed | Published05/20/2016 | SeverityUnknown |
CVE-2016-3705 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2016 | SeverityUnknown |
CVE-2016-3627 | Exploitation statusNot known exploited | FixNot confirmed | Published05/17/2016 | SeverityHigh |
CVE-2015-6837 | Exploitation statusNot confirmed | FixNot confirmed | Published05/16/2016 | SeverityUnknown |
CVE-2015-6838 | Exploitation statusNot confirmed | FixNot confirmed | Published05/16/2016 | SeverityUnknown |
CVE-2015-8806 | Exploitation statusNot confirmed | FixNot confirmed | Published04/13/2016 | SeverityUnknown |
CVE-2015-8710 | Exploitation statusNot confirmed | FixNot confirmed | Published04/11/2016 | SeverityUnknown |
CVE-2016-1762 | Exploitation statusNot known exploited | FixNot confirmed | Published03/24/2016 | SeverityHigh |
CVE-2016-2073 | Exploitation statusNot confirmed | FixNot confirmed | Published02/12/2016 | SeverityUnknown |
CVE-2015-7499 | Exploitation statusNot confirmed | FixNot confirmed | Published12/15/2015 | SeverityUnknown |
CVE-2015-8317 | Exploitation statusNot confirmed | FixNot confirmed | Published12/15/2015 | SeverityUnknown |
CVE-2015-5312 | Exploitation statusNot confirmed | FixNot confirmed | Published12/15/2015 | SeverityUnknown |
CVE-2015-7498 | Exploitation statusNot confirmed | FixNot confirmed | Published12/15/2015 | SeverityUnknown |
CVE-2015-7500 | Exploitation statusNot confirmed | FixNot confirmed | Published12/15/2015 | SeverityUnknown |
CVE-2015-8241 | Exploitation statusNot confirmed | FixNot confirmed | Published12/15/2015 | SeverityUnknown |
CVE-2015-8242 | Exploitation statusNot confirmed | FixNot confirmed | Published12/15/2015 | SeverityUnknown |
CVE-2015-7497 | Exploitation statusNot confirmed | FixNot confirmed | Published12/15/2015 | SeverityUnknown |
CVE-2015-7941 | Exploitation statusNot confirmed | FixNot confirmed | Published11/18/2015 | SeverityUnknown |
CVE-2015-8035 | Exploitation statusNot confirmed | FixNot confirmed | Published11/18/2015 | SeverityUnknown |
CVE-2015-7942 | Exploitation statusNot confirmed | FixNot confirmed | Published11/18/2015 | SeverityUnknown |
CVE-2014-3660 | Exploitation statusNot confirmed | FixNot confirmed | Published11/04/2014 | SeverityUnknown |
CVE-2013-0339 | Exploitation statusNot confirmed | FixNot confirmed | Published01/21/2014 | SeverityUnknown |
CVE-2013-2877 | Exploitation statusNot confirmed | FixNot confirmed | Published07/10/2013 | SeverityUnknown |
CVE-2013-0338 | Exploitation statusNot confirmed | FixNot confirmed | Published04/25/2013 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan