CVE-2026-15168 is an information-disclosure vulnerability in Wireshark's BLF zlib LogContainer parser. The parser allocates a non-zero-initialized buffer using an attacker-controlled declared uncompressed size, but accepts successful zlib stream termination without verifying that the actual decompressed output size equals the declared size. Subsequent BLF object parsing treats the declared size as authoritative and can consume the unread buffer tail, exposing uninitialized heap contents as decoded packet data. The issue affects Wireshark 4.6.0 through 4.6.6 and 4.4.0 through 4.4.16.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Wireshark vulnerability referenced by the plugin; no individual technical details are provided.
A Wireshark vulnerability referenced by the plugin; no technical description is provided.
A possible information-disclosure vulnerability in Wireshark's BLF file parser.
A Wireshark BLF file-parser vulnerability that may permit information disclosure.
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.