PatchSiren cyber security CVE debrief
CVE-2026-14164 Red Hat CVE debrief
A double free issue was identified in libarchive's RAR5 reader. During parsing of a specially crafted RAR5 archive, the filtered_buf pointer may remain stale after being freed during unpacking state reinitialization. Subsequent processing of another archive entry can trigger a second free of the same memory region, resulting in a double-free condition.
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 10
- CVSS
- HIGH 7.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-06-30
- Original CVE updated
- 2026-08-10
- Advisory published
- 2026-06-30
- Advisory updated
- 2026-08-10
Who should care
Developers and administrators using libarchive in their applications, especially those handling RAR5 archives, should be aware of this vulnerability and take steps to mitigate it. They should assess their exposure, review vendor guidance, and apply patches or updates when available. Additionally, they should monitor for and respond to potential denial of service attempts. Security teams and vulnerability management teams should prioritize this vulnerability due to its potential impact on service availability and take proactive measures to protect their environments. Operators of affected platforms should also be aware of the potential for denial of service and take steps to minimize their exposure. This may involve reviewing system logs for signs of exploitation and implementing compensating controls where necessary. The vulnerability's impact on service availability could be significant, making it essential for affected organizations to take prompt action to mitigate the risk. Security teams should work closely with system administrators and developers to ensure that patches are applied and that systems are properly configured to prevent exploitation. By taking these steps, organizations can reduce their risk of exposure to this vulnerability and protect their services from potential denial of service attacks. The double free issue in libarchive's RAR5 reader could have far-reaching consequences if not addressed promptly, emphasizing the need for swift action to mitigate the vulnerability. Therefore, it is crucial for all stakeholders to be aware of this issue and take proactive measures to prevent potential attacks. This includes reviewing system configurations, applying patches, and monitoring system logs for signs of exploitation. By working together, organizations can minimize the risk associated with this vulnerability and protect their services from potential attacks. The potential impact of this vulnerability on service availability highlights the importance of prioritizing its mitigation and taking proactive steps to prevent exploitation. Organizations should not delay in addressing this vulnerability, as the consequences of a successful attack could be
Technical summary
A double free issue was identified in libarchive's RAR5 reader. During parsing of a specially crafted RAR5 archive, the filtered_buf pointer may remain stale after being freed during unpacking state reinitialization. Subsequent processing of another archive entry can trigger a second free of the same memory region, resulting in a double-free condition. Successful exploitation may cause applications using the vulnerable libarchive API to terminate unexpectedly, leading to a denial of service.
Defensive priority
High priority due to potential for denial of service
Recommended defensive actions
- Inventory and assess libarchive usage in your environment
- Apply patches or updates from the vendor when available
- Monitor for and respond to potential denial of service attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
Evidence from official sources indicates a double free issue in libarchive's RAR5 reader. Limited information is available on affected products and versions. The filtered_buf pointer may remain stale after being freed during unpacking state reinitialization. Subsequent processing of another archive entry can trigger a second free of the same memory region, resulting in a double-free condition. Successful exploitation may cause applications using the vulnerable libarchive API to terminate unexpectedly, leading to a denial of service. Developers and administrators should verify their usage of libarchive and assess potential exposure.
Official resources
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-06-30T07:16:32.170Z and has not been modified since then.