VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libarchive: vulnerability history, versions and safety

libarchive is a package in the Debian ecosystem. Vulert records 130 vulnerabilities for it across 24 releases, from Nov -0001 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
130 vulnerabilities recorded U130
i
19 with no fix published

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

See the unfixed vulnerabilities →
i
6 in the last 12 months

Most recent disclosure 21 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libarchive vulnerabilities

Vulert verdict on libarchive i

Updated on 23 Oct 2026

Careful: 19 of the 130 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 130 vulnerabilities on record across 2026 years, 6 in the last year.

What to do: Plan around the 19 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 130 over 2026 years · 6 in the last year i
  • Latest disclosure 21 Jul 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 19 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 libarchive, 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 24 of 24 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 4
  • 2006 2
  • 2007 6
  • 2012 8
  • 2013 2
  • 2015 2
  • 2016 49
  • 2017 17
  • 2018 8
  • 2019 7
  • 2020 1
  • 2021 1
  • 2022 5
  • 2023 2
  • 2024 3
  • 2025 9
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for libarchive

The 5 most severe of 130 vulnerabilities recorded for this package

Search all 130 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Out-of-Bounds Access Vulnerability in Libarchive: CVE-2024-37407 9.1 critical No fix published 08 Jun 2024
CVE-2018-1000877: Double Free Vulnerability in libarchive RAR Decoder 8.8 high 3.3.3-2 20 Dec 2018
CVE-2018-1000878: Use After Free Vulnerability in libarchive RAR Decoder 8.8 high 3.3.3-2 20 Dec 2018
Critical Stack-Based Buffer Overflow in libarchive: CVE-2016-4301 7.8 high 3.2.1-1 21 Sep 2016
Improper Link Resolution in libarchive: A Critical ACL Vulnerability 7.8 high 3.4.3-2+deb11u1 23 Aug 2022

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 libarchive

Is libarchive safe to use?

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

How many vulnerabilities does libarchive have?

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

6 vulnerabilities were recorded for libarchive in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. 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 libarchive 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 libarchive for upcoming vulnerabilities?

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