VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libarchive: vulnerability history, versions and safety

libarchive is a package in the Debian ecosystem. Vulert records 10 vulnerabilities for it across 23 releases, from Apr 2024 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded U10
i
1 with no fix published

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

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

Most recent disclosure 17 Oct 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: one of the 10 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 10 vulnerabilities on record across 2 years, 1 in the last year.

What to do: Plan around the 1 vulnerability 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 10 over 2 years · 1 in the last year i
  • Latest disclosure 17 Oct 2026 i
  • Highest CVSS n/a i
  • With no published fix 1 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 23 of 23 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 5
  • 2025 4
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for libarchive

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Security Update for libarchive N/A unrated 3.6.2-1+deb12u1 05 Jun 2024
Critical Security Update for libarchive: Addressing CVE-2024-20696 N/A unrated 3.6.2-1+deb12u2 09 Nov 2024
Critical Remote Code Execution Vulnerability in libarchive N/A unrated 3.6.2-1+deb12u1 09 Apr 2024
Out-of-Bounds Access Vulnerability in libarchive - CVE-2024-48957 N/A unrated 3.6.2-1+deb12u1 10 Oct 2024
Out-of-Bounds Access Vulnerability in libarchive Package N/A unrated 3.6.2-1+deb12u1 10 Oct 2024

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 10 vulnerabilities for libarchive in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 10 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does libarchive have?

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

1 vulnerability was recorded for libarchive in the last 12 months, and the oldest entry in this database dates to 09 Apr 2024. 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.