VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

libxslt: vulnerability history, versions and safety

libxslt is a package in the OSS-Fuzz ecosystem. Vulert records 12 vulnerabilities for it across 10 affected ranges, from Jul 2020 to Apr 2023. 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 H2 M10
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 libxslt vulnerabilities

Vulert verdict on libxslt i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 12 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 12 over 2 years · 0 in the last year i
  • Latest disclosure 01 Apr 2023 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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from 311da8c8864e4f4f838434d769e0644cc02c9da9 up to 2232473733b7313d67de8836ea3b29eec6e8e285 (exclusive) 2
from 7f56378a73af8a61da78b8091f0e317316cee300 up to 2232473733b7313d67de8836ea3b29eec6e8e285 (exclusive) 1
from 93407f6d3234ae3f036154d69f07da291eff34ff up to 677b2e8fe8187f3ba981dc97f65e75fec2dec62c (exclusive) 1
from 7f56378a73af8a61da78b8091f0e317316cee300 up to 9d4bfeecbdf28f3980b23fa8f2504bdf54f04486 (exclusive) 2
from 7f56378a73af8a61da78b8091f0e317316cee300 up to 6ce8de69330783977dd14f6569419489875fb71b (exclusive) 1
from 7f56378a73af8a61da78b8091f0e317316cee300 up to 01f8317dd8ffe2141fae0348edd9fd51037ee41b (exclusive) 1
from 93407f6d3234ae3f036154d69f07da291eff34ff up to ac9d752240d399db1d7c09f2ef4008200a272c8c (exclusive) 1
from 569328d95d418f10067bb5915147d600986f9058 up to f80ae929fa9e80d66d4c42108c6fb2456ce14b8b (exclusive) 1
from 7f56378a73af8a61da78b8091f0e317316cee300 up to c5eb6cf3aba0af048596106ed839b4ae17ecbcb1 (exclusive) 1
from 7f56378a73af8a61da78b8091f0e317316cee300 up to e1f8d2e6eb1167fd51eb5b8c99d2d40c37299897 (exclusive) 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 9
  • 2023 3

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 libxslt

The 5 most severe of 12 vulnerabilities recorded for this package

Search all 12 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-double-free vulnerability in libxslt N/A high ac9d752240d399db1d7c09f2ef4008200a272c8c 16 Mar 2023
Use-of-uninitialized-value in xmlOutputBufferWriteEscape in libxslt N/A medium 2232473733b7313d67de8836ea3b29eec6e8e285 01 Jul 2020
Use-of-uninitialized-value in libxslt: xmlOutputBufferWriteEscape N/A medium 2232473733b7313d67de8836ea3b29eec6e8e285 01 Jul 2020
Index-out-of-bounds in xsltSetAttrVTsegment in libxslt N/A medium 01f8317dd8ffe2141fae0348edd9fd51037ee41b 22 Jul 2020
Use-of-uninitialized-value in xmlSwitchEncoding in libxslt N/A medium f80ae929fa9e80d66d4c42108c6fb2456ce14b8b 27 Mar 2023

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 12 vulnerabilities for libxslt in OSS-Fuzz: 0 critical, 2 high, 10 medium and 0 low. 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 libxslt have?

12 vulnerabilities are recorded for libxslt in the OSS-Fuzz ecosystem: 0 critical, 2 high, 10 medium and 0 low. 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 01 Jul 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 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.