Loading vulnerability…
CVE-2026-40930 is a chunk-smuggling flaw in the push-mode APNG parser derived from the third-party libpng-apng patch and present in the libpng 1.8.0 development branch (libpng18). The bug occurs in three inter-frame chunk discard paths where the parser clears the chunk-header flag without consuming the discarded chunk body and CRC. As a result, attacker-controlled bytes remaining inside the discarded chunk can be reinterpreted as a fresh PNG chunk header on the next call to png_process_data. This creates an interpretation-conflict condition in which parser state becomes desynchronized from the actual input stream. The issue affects only push-mode parsing via png_process_data; sequential-mode parsing using png_read_info, png_read_row, and png_read_end is not affected. Upstream libpng 1.6.x releases are not affected unless a downstream consumer applies vulnerable libpng-apng patch revisions.
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.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.