VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

libxml2: vulnerability history, versions and safety

libxml2 is a package in the OSS-Fuzz ecosystem. Vulert records 56 vulnerabilities for it across 47 releases, from Jun 2020 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
56 vulnerabilities recorded H31 M6 U19
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 12 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libxml2 vulnerabilities

Vulert verdict on libxml2 i

Updated on 23 Oct 2026

Careful: 2 of the 56 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 56 vulnerabilities on record across 5 years, 1 in the last year.

What to do: Plan around the 2 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 56 over 5 years · 1 in the last year i
  • Latest disclosure 12 Apr 2026 i
  • Highest CVSS n/a i
  • With no published fix 2 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for libxml2, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 47 of 47 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 8
  • 2021 1
  • 2022 2
  • 2023 31
  • 2024 11
  • 2025 2
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 56 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for libxml2

The 5 most severe of 56 vulnerabilities recorded for this package

Search all 56 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-buffer-overflow in libxml2: xmlDictLookupInternal N/A medium 71aae4e98b7e325463e528242ca363b0380a6c92 03 Oct 2023
Heap-use-after-free vulnerability in libxml2: xmlTextReaderRead N/A high ba589adc2f86c6be9ad7e0d771d4c9b09d059b89 27 Aug 2020
Heap-use-after-free vulnerability in libxml2: xmlStaticCopyNode N/A high 97e99f411228fe4f65ebb60e4f2c56f9ee9cdb1c 06 Oct 2023
Heap Buffer Overflow in libxml2: Critical Vulnerability Detected N/A medium a7511af09f99995cdf81994db21f4eba564276b5 12 Apr 2026
Heap-use-after-free vulnerability in libxml2: xmlRemoveID N/A high 1a66b176055d25ee635bf328c7b35b381db0b71d 06 Feb 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About libxml2

Is libxml2 safe to use?

Vulert records 56 vulnerabilities for libxml2 in OSS-Fuzz: 0 critical, 31 high, 6 medium and 0 low, plus 19 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libxml2 have?

56 vulnerabilities are recorded for libxml2 in the OSS-Fuzz ecosystem: 0 critical, 31 high, 6 medium and 0 low, plus 19 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new libxml2 vulnerabilities disclosed?

1 vulnerability was recorded for libxml2 in the last 12 months, and the oldest entry in this database dates to 24 Jun 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of libxml2 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor libxml2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the libxml2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.