Loading vulnerability…
CVE-2026-48102 is a heap out-of-bounds read in 7-Zip’s UDF disc image handler affecting versions 9.11 through 26.00. The flaw is in the File Identifier Descriptor parser, specifically CFileId::Parse in CPP/7zip/Archive/Udf/UdfIn.cpp. After validating that the record size is less than 38 + idLen + impLen and advancing the processed offset to 38 + impLen + idLen, the parser enters an alignment-padding loop intended to advance to a 4-byte boundary. That loop reads p[processed] while incrementing processed up to three times, but the processed <= size bounds check is performed only after the loop completes. If the parsed structure is exactly sized so that 38 + impLen + idLen equals the heap buffer size and the offset is not already 4-byte aligned, the loop reads 1 to 3 bytes past the end of the heap allocation created for the directory entry buffer. The vulnerable code path is reachable when 7-Zip opens, lists, or extracts a crafted UDF image. Because the UDF handler is associated with optical-disc image parsing and can be selected by file type or signature-based detection, exploitation can occur during normal archive processing of a malicious UDF-backed image.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.