CVE-2026-4111 is an infinite-loop vulnerability in libarchive's RAR5 decompression processing path reached through archive_read_data(). A specially crafted but checksum-valid RAR5 archive can cause the decompression logic to enter a state in which it cannot make forward progress, continuously consuming CPU resources. The archive can appear structurally valid, preventing affected applications from identifying the condition before attempting decompression.
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.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A libarchive RAR5 decompression flaw that can cause an infinite loop and denial of service through archive_read_data().
A libarchive vulnerability causing infinite-loop denial of service during RAR5 decompression via archive_read_data().
A libarchive denial-of-service vulnerability causing an infinite loop during RAR5 decompression via archive_read_data().
An infinite-loop denial-of-service vulnerability in libarchive RAR5 decompression through archive_read_data().
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.