CVE-2025-64720
7.1LIBPNG · libpng
An out-of-bounds read vulnerability exists in libpng versions 1.6.0 through 1.6.50 within the png_image_read_composite function when processing specific palette images.
Executive summary
A critical out-of-bounds read vulnerability in libpng versions 1.6.0 through 1.6.50 allows unauthenticated remote attackers to potentially cause a denial of service or information disclosure.
Vulnerability
The flaw is an out-of-bounds read occurring in the png_image_read_composite function due to incorrect background compositing logic during premultiplication. This vulnerability can be triggered by an unauthenticated attacker providing a maliciously crafted PNG image to an application using the affected library.
Business impact
The vulnerability carries a CVSS score of 7.1, indicating a high severity. Successful exploitation could lead to an application crash, resulting in service disruption, or potentially expose sensitive memory contents to an attacker. Given that libpng is a foundational library used across countless software ecosystems, the potential for widespread operational impact is significant.
Remediation
Immediate Action: Update the libpng library to version 1.6.51 or later across all affected systems and applications.
Proactive Monitoring: Monitor application logs for unexpected crashes or error messages related to image processing functions, particularly when handling untrusted user-supplied files.
Compensating Controls: Implement strict input validation and sanitization for image uploads to ensure only well-formed files are processed by the library. Consider running image processing tasks in sandboxed or isolated containers to limit the impact of potential memory corruption.
Exploitation status
Public Exploit Available: Unknown
Analyst recommendation
Organizations should prioritize the identification of software components utilizing libpng versions 1.6.0 through 1.6.50. Due to the library's ubiquity and the existence of a proof-of-concept, the risk of exploitation is elevated. Updating to version 1.6.51 is the only effective way to remediate this memory corruption flaw and should be performed during the next scheduled maintenance window or sooner for mission-critical systems.