VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libxml2: vulnerability history, versions and safety

libxml2 is a package in the Debian ecosystem. Vulert records 12 vulnerabilities for it across 14 releases, from Jul 2014 to Dec 2017. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
12 vulnerabilities recorded U12
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

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 22 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 18 Dec 2017. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 12 vulnerabilities on record across 3 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 12 over 3 years · 0 in the last year i
  • Latest disclosure 18 Dec 2017 i
  • Highest CVSS n/a i
  • With no published fix 0 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 14 of 14 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 2
  • 2015 3
  • 2016 2
  • 2017 5

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

03 Vulnerabilities

Recorded vulnerabilities for libxml2

The 5 most severe of 12 vulnerabilities recorded for this package

Search all 12 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in libxml2 N/A unrated 2.8.0+dfsg1-7+wheezy2 26 Oct 2014
DSA-2978-1: libxml2 - Denial of Service Vulnerability N/A unrated 2.8.0+dfsg1-7+wheezy1 11 Jul 2014
Denial of Service Vulnerability in libxml2 N/A unrated 2.8.0+dfsg1-7+wheezy3 06 Feb 2015
Security Update for libxml2 Package N/A unrated 2.8.0+dfsg1-7+wheezy7 31 Oct 2016
Denial of Service Vulnerability in libxml2 N/A unrated 2.8.0+dfsg1-7+wheezy4 07 Apr 2015

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 12 vulnerabilities for libxml2 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 12 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does libxml2 have?

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

0 vulnerabilities were recorded for libxml2 in the last 12 months, and the oldest entry in this database dates to 11 Jul 2014. 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.