CVE-2025-5916: Libarchive: integer overflow while reading warc files at archive_read_support_format_warc.c
A vulnerability has been identified in the libarchive library. This flaw involves an integer overflow that can be triggered when processing a Web Archive (WARC) file that claims to have more than INT64MAX - 4 content bytes. An attacker could craft a malicious WARC archive to induce this overflow, potentially leading to unpredictable program behavior, memory corruption, or a denial-of-service condition within applications that process such archives using libarchive. This bug affects libarchive versions prior to 3.8.0.
Other sources
In libarchive before 3.8.0, a warc archive that claims to have more than INT64MAX - 4 content bytes may lead to an integer overflow.
— Red Hat
Libarchive: integer overflow while reading warc files at archivereadsupportformatwarc.c
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.30.3-8 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.7.7-3 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.6.1-7 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.21.4-20 - Upgrade
Upgrade
libarchiveto a version that resolves this vulnerability.Fixed in 3.8.0
Event History
Frequently Asked Questions
What is the severity of CVE-2025-5916?
CVE-2025-5916 has been classified with a high severity due to the potential for remote code execution from an integer overflow.
How do I fix CVE-2025-5916?
To fix CVE-2025-5916, you should update to the latest version of the libarchive library where the vulnerability has been addressed.
What types of systems are affected by CVE-2025-5916?
CVE-2025-5916 affects systems that utilize the libarchive library to process Web Archive (WARC) files.
What kind of attack can be executed using CVE-2025-5916?
An attacker could exploit CVE-2025-5916 to craft a malicious WARC file, potentially leading to memory corruption and executing arbitrary code.
Is there a workaround for CVE-2025-5916?
As of now, the best approach is to apply the patch for CVE-2025-5916 since there are no reliable workarounds available.