Interpretation Conflict Affecting libpng package, versions [0,]
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CONAN-LIBPNG-17223249
- published7 Jun 2026
- disclosed4 Jun 2026
- creditSeung Min Shin
Introduced: 4 Jun 2026
NewCVE-2026-40930 (opens in a new tab)How to fix?
There is no fixed version for libpng.
Overview
Affected versions of this package are vulnerable to Interpretation Conflict in the png_push_read_chunk() function in the push-mode APNG parser. An attacker can inject chunked data with a malicious PNG file containing attacker-controlled bytes in an ignored ancillary chunk, which are then reinterpreted as a new chunk header on subsequent processing. In standard configurations, this triggers a png_error, which crashes before the data gets passed on to the application. However, if CRC error handling is configured to a non-default value via png_set_crc_action the frame count mismatch can be ignored and an attacker controlled image rendered as a result.
Note: This vulnerability was introduced with the incorporation of the libpng-apng patch, as of release branch 1.6. Users of that branch, in addition to the linked fix, should also apply an additional fdAT chunk patch to address this vulnerability.