Loading vulnerability…
CVE-2026-34757 is a use-after-free vulnerability in libpng affecting the chunk setter APIs png_set_PLTE, png_set_tRNS, and png_set_hIST. When an application passes a pointer previously obtained from png_get_PLTE, png_get_tRNS, or png_get_hIST back into the corresponding setter on the same png_struct/png_info pair, the setter frees the internal buffer before copying from the caller-supplied pointer. Because the supplied pointer aliases the just-freed internal buffer, the subsequent copy reads from freed memory. This can result in silently corrupted PNG chunk metadata or copying unrelated heap contents into the replacement chunk buffer. The png_set_PLTE and png_set_tRNS variants affect libpng 1.6.56 as regressions, while the png_set_hIST issue has existed since at least libpng 1.0.9. The issue is fixed in libpng 1.6.57.
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.
11 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.