VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libxslt: vulnerability history, versions and safety

libxslt is a package in the Debian ecosystem. Vulert records 52 vulnerabilities for it across 12 releases, from May 2008 to Oct 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
52 vulnerabilities recorded U52
i
8 with no fix published

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

See the unfixed vulnerabilities →
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 libxslt vulnerabilities

Vulert verdict on libxslt i

Updated on 23 Oct 2026

Careful: 8 of the 52 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 52 vulnerabilities on record across 17 years, none in the last year.

What to do: Plan around the 8 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 52 over 17 years · 0 in the last year i
  • Latest disclosure 14 Oct 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 8 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 libxslt, 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 12 of 12 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2008 4
  • 2011 2
  • 2012 10
  • 2013 2
  • 2015 2
  • 2016 14
  • 2017 3
  • 2019 4
  • 2022 1
  • 2023 1
  • 2025 9

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

03 Vulnerabilities

Recorded vulnerabilities for libxslt

The 5 most severe of 52 vulnerabilities recorded for this package

Search all 52 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Memory Corruption Vulnerability in libxslt Affects Multiple Apple Platforms 9.8 critical 1.1.29-1 22 Jul 2016
Memory Corruption Vulnerability in libxslt: Denial of Service Risk 9.8 critical 1.1.29-1 22 Jul 2016
Critical Memory Corruption Vulnerability in libxslt Affects Multiple Apple Platforms 9.8 critical 1.1.29-1 22 Jul 2016
Critical Remote Code Execution Vulnerability in libxslt Affects Multiple Apple Platforms 8.8 high 1.1.29-2 25 Sep 2016
Critical Remote Code Execution Vulnerability in libxslt 8.8 high 1.1.29-1 20 May 2016

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 libxslt

Is libxslt safe to use?

Vulert records 52 vulnerabilities for libxslt in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 52 not yet rated. 8 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libxslt have?

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

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

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