CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-25646 remediation guide

pnggroup libpng, OPENJDK ELS 11.0.31, Red Hat Build of OpenJDK 17.0.9

LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to 1.6.55, an out-of-bounds read vulnerability exists in the png_set_quantize() API function. When the function is called with no histogram and the number of colors in the palette is more than twice the maximum supported by the user's display, certain palettes will cause the function to enter into an infinite loop that reads past the end of an internal heap-allocated buffer. The images that trigger this vulnerability are valid per the PNG specific...

Open CVE record
Productpnggroup libpng, OPENJDK ELS 11.0.31, Red Hat Build of OpenJDK 17.0.9
Affected versions>= < 1.6.55, < 1.6.55
Fixed versions1.6.55
Priority basisReview · CVSS 8.3 · EPSS 0.95%
01

Identify the affected asset

Confirm whether pnggroup libpng, OPENJDK ELS 11.0.31, Red Hat Build of OpenJDK 17.0.9 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= < 1.6.55, < 1.6.55. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 1.6.55. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.