CVE-2026-14164 is a double-free vulnerability in libarchive's RAR5 decompression logic. When libarchive parses a specially crafted RAR5 archive, the RAR5 reader can free the internal filtered_buf buffer during unpacking state reinitialization in init_unpack() while leaving the pointer stale. If processing then continues to another archive entry, the same memory region may be freed again, creating a double-free condition in the RAR5 reader. The flaw affects applications that use the vulnerable libarchive API to inspect or extract attacker-controlled RAR5 content.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A double-free vulnerability in libarchive's RAR5 decompression logic caused by a dangling filtered_buf pointer in init_unpack(), affecting Red Hat Enterprise Linux 9 libarchive packages.
A double-free vulnerability in libarchive's RAR5 decompression logic caused by a dangling filtered_buf pointer in init_unpack(), affecting Red Hat Enterprise Linux 9 systems with vulnerable libarchive packages installed.
A double-free vulnerability in libarchive's RAR5 decompression logic caused by a dangling filtered_buf pointer in init_unpack().
A double-free vulnerability in libarchive's RAR5 decompression logic caused by a dangling filtered_buf pointer in init_unpack().
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.