Is libxls safe to use?

Vulert records 1 vulnerabilities for libxls in OSS-Fuzz: 0 critical, 0 high, 1 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 libxls have?

1 vulnerability is recorded for libxls in the OSS-Fuzz ecosystem: 0 critical, 0 high, 1 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 libxls vulnerabilities disclosed?

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

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

Vulnerability Database · OSS-Fuzz · Package report

libxls: vulnerability history, versions and safety

libxls is a package in the OSS-Fuzz ecosystem. Vulert records 1 vulnerability for it across 1 affected range, first recorded in Jul 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

1 vulnerabilities recorded M1

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libxls vulnerabilities

Vulert verdict on libxls i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 1 vulnerability on record across 1 year, 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 1 over 1 year · 0 in the last year i
Latest disclosure 22 Jul 2020 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.

Scan your app free →

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.

Affected range	Vulnerabilities
from 59d46ecc398f26a2dd5b94e599168df3d54ab478 up to 5d88fc8514937e87555981a219ab8d2556e0ec75 (exclusive)	1

02 Disclosure history

How often vulnerabilities are recorded

2020 1

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

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for libxls

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
Heap-buffer-overflow in libxls: xls_isCellTooSmall	N/A medium	5d88fc8514937e87555981a219ab8d2556e0ec75	22 Jul 2020

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