VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libxml-libxml-perl: vulnerability history, versions and safety

libxml-libxml-perl is a package in the Debian ecosystem. Vulert records 2 vulnerabilities for it across 2 releases, from May 2015 to Nov 2017. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded U2
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 libxml-libxml-perl vulnerabilities

Vulert verdict on libxml-libxml-perl i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 2 vulnerabilities on record across 2 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 2 over 2 years · 0 in the last year i
  • Latest disclosure 14 Nov 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 libxml-libxml-perl, 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.0001+dfsg-1 U2 Yes Details →
2.0001+dfsg-1+deb7u1 U1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2015 1
  • 2017 1

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

03 Vulnerabilities

Recorded vulnerabilities for libxml-libxml-perl

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Vulnerability in libxml-libxml-perl - Use-After-Free N/A unrated 2.0001+dfsg-1+deb7u2 14 Nov 2017
Vulnerability in libxml-libxml-perl - Security Update N/A unrated 2.0001+dfsg-1+deb7u1 01 May 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: 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 libxml-libxml-perl

Is libxml-libxml-perl safe to use?

Vulert records 2 vulnerabilities for libxml-libxml-perl in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 2 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 libxml-libxml-perl have?

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

0 vulnerabilities were recorded for libxml-libxml-perl in the last 12 months, and the oldest entry in this database dates to 01 May 2015. 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 libxml-libxml-perl 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 libxml-libxml-perl for upcoming vulnerabilities?

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