Widely used PNG library; affects many apps across industries; potential disruption to image processing.
CVE-2026-25646
Out-of-bounds read in libpng png_set_quantize() causes infinite loop on certain PNGs.
Is CVE-2026-25646 being exploited?
Not confirmed. CVE-2026-25646 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.97% probability of exploitation in the next 30 days.
How severe is CVE-2026-25646?
CVE-2026-25646 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-25646?
Yes. A fix has been recorded for CVE-2026-25646. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-25646 affect?
CVE-2026-25646 affects libpng <= 1.6.54, apps using libpng. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-25646?
Upgrade to libpng 1.6.55 or later
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
DoS via crafted PNGs causing CPU/memory exhaustion and crash in affected apps.
Patch when possible
- affected< 1.6.55
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.