Vulnerability Database · Debian · Package report

libxml2: vulnerability history, versions and safety

libxml2 is a package in the Debian ecosystem. Vulert records 201 vulnerabilities for it across 68 releases, from Nov -0001 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
201 vulnerabilities recorded U201
i
12 with no fix published

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

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

Most recent disclosure 29 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on libxml2 i

Updated on 23 Oct 2026

Careful: 12 of the 201 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 201 vulnerabilities on record across 2026 years, 4 in the last year.

What to do: Plan around the 12 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 201 over 2026 years · 4 in the last year i
  • Latest disclosure 29 Jun 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 12 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.

i
Version Vulert vulnerabilities Fix published Details
2.15.3+dfsg-1 U2 No Details →
2.15.2+dfsg-0.1 U3 No Details →
2.15.1+dfsg-2 U7 No Details →
2.15.1+dfsg-1 U7 No Details →
2.15.1+dfsg-0.5 U7 No Details →
2.15.1+dfsg-0.4 U7 No Details →
2.15.1+dfsg-0.3 U8 No Details →
2.15.1+dfsg-0.2 U8 No Details →
2.15.1+dfsg-0.1 U8 No Details →
2.15.0+dfsg-0.3 U8 No Details →
2.15.0+dfsg-0.2 U8 No Details →
2.15.0+dfsg-0.1 U8 No Details →
2.14.6+dfsg-0.1 U8 No Details →
2.14.5+dfsg-0.2 U11 No Details →
2.14.5+dfsg-0.1 U12 No Details →
2.14.5+dfsg-0exp2 U12 No Details →
2.14.5+dfsg-0exp1 U12 No Details →
2.14.4+dfsg-0exp1 U12 No Details →
2.14.3+dfsg-0exp3 U12 No Details →
2.14.3+dfsg-0exp2 U12 No Details →
2.14.3+dfsg-0exp1 U12 No Details →
2.14.2+dfsg-0exp1 U12 No Details →
2.14.1+dfsg-0exp1 U12 No Details →
2.13.3+dfsg-0exp2 U12 No Details →
2.13.3+dfsg-0exp1 U12 No Details →
2.13.1+dfsg-0exp1 U12 No Details →
2.12.7+dfsg-3 U12 No Details →
2.12.7+dfsg-2 U12 No Details →
2.12.7+dfsg-1 U12 No Details →
2.12.7+dfsg+really2.9.14-2.1 U12 No Details →
2.12.7+dfsg+really2.9.14-2 U12 No Details →
2.12.7+dfsg+really2.9.14-1 U12 No Details →
2.12.7+dfsg+really2.9.14-0.4 U12 No Details →
2.12.7+dfsg+really2.9.14-0.3 U12 No Details →
2.12.7+dfsg+really2.9.14-0.2 U12 No Details →
2.12.7+dfsg+really2.9.14-0.1 U12 No Details →
2.12.6+dfsg-0exp2 U12 No Details →
2.12.6+dfsg-0exp1 U12 No Details →
2.12.5+dfsg-0exp1 U12 No Details →
2.12.3+dfsg-0exp1 U12 No Details →
2.9.14+dfsg-1.3 U12 No Details →
2.9.14+dfsg-1.3~deb12u6 U2 No Details →
2.9.14+dfsg-1.3~deb12u5 U7 No Details →
2.9.14+dfsg-1.3~deb12u4 U11 No Details →
2.9.14+dfsg-1.3~deb12u3 U12 No Details →
2.9.14+dfsg-1.3~deb12u2 U12 No Details →
2.9.14+dfsg-1.3~deb12u1 U12 No Details →
2.9.14+dfsg-1.2 U12 No Details →
2.9.14+dfsg-1.1 U12 No Details →
2.9.14+dfsg-1 U12 No Details →
2.9.13+dfsg-1 U12 No Details →
2.9.12+dfsg-6 U12 No Details →
2.9.12+dfsg-5 U12 No Details →
2.9.12+dfsg-4 U12 No Details →
2.9.12+dfsg-3 U12 No Details →
2.9.12+dfsg-2 U12 No Details →
2.9.12+dfsg-1 U12 No Details →
2.9.10+dfsg-6.7 U48 No Details →
2.9.10+dfsg-6.7+deb11u10 U2 No Details →
2.9.10+dfsg-6.7+deb11u9 U8 No Details →
2.9.10+dfsg-6.7+deb11u8 U13 No Details →
2.9.10+dfsg-6.7+deb11u7 U23 No Details →
2.9.10+dfsg-6.7+deb11u6 U26 No Details →
2.9.10+dfsg-6.7+deb11u5 U37 No Details →
2.9.10+dfsg-6.7+deb11u4 U40 No Details →
2.9.10+dfsg-6.7+deb11u3 U43 No Details →
2.9.10+dfsg-6.7+deb11u2 U46 No Details →
2.9.10+dfsg-6.7+deb11u1 U47 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 0 4
  • 2004 2
  • 2005 2
  • 2008 10
  • 2009 4
  • 2010 4
  • 2011 10
  • 2012 10
  • 2013 4
  • 2014 4
  • 2015 26
  • 2016 38
  • 2017 17
  • 2018 12
  • 2019 1
  • 2020 3
  • 2021 6
  • 2022 7
  • 2023 7
  • 2024 3
  • 2025 24
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for libxml2

The 5 most severe of 201 vulnerabilities recorded for this package

Search all 201 in the database →

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 201 vulnerabilities for libxml2 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 201 not yet rated. 12 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libxml2 have?

201 vulnerabilities are recorded for libxml2 in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 201 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?

4 vulnerabilities were recorded for libxml2 in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. 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.