dbcve.org
LibarchiveApplication

CVE-2025-1632

MEDIUM · 5.5 CVSS v3.1 Published 2025-02-24
Fix available
A fix is available. Upgrade to after 3.7.7 or later.
See remediation →
57/100
Remediation priority · Elevated
Public exploit Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in libarchive up to 3.7.7. It has been classified as problematic. This affects the function list of the file bsdunzip.c. The manipulation leads to null pointer dereference. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LibarchiveApplication
Affected:<= 3.7.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.7.7
Recommended fix Moderate confidence

libarchive 3.7.8 or later (latest stable release)

  1. 1. Identify the current libarchive version installed on your system using your package manager or by running `libarchive --version` or checking library version
  2. 2. For Debian/Ubuntu-based systems: Run `sudo apt-get update && sudo apt-get install libarchive13` to get the latest available version
  3. 3. For Red Hat/CentOS/Fedora-based systems: Run `sudo yum update libarchive` or `sudo dnf update libarchive`
  4. 4. For Alpine-based systems: Run `apk add --upgrade libarchive`
  5. 5. For macOS using Homebrew: Run `brew update && brew upgrade libarchive`
  6. 6. If installing from source, download libarchive 3.7.8 or later from the official GitHub releases page and rebuild
  7. 7. Verify the upgrade was successful by checking the new version
  8. 8. Test your applications that depend on libarchive to ensure functionality is intact
Caveat Minor: Ensure any custom code using libarchive API is compatible with the latest version; review release notes for API changes

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1632 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1632 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data