CVE-2026-33636: LIBPNG has ARM NEON Palette Expansion Out-of-Bounds Read on AArch64

Published Mar 26, 2026
·
Updated

In pngdoexpandpalettergba8neon of paletteneonintrinsics.c, there is a possible out of bounds read and write due to an incorrect bounds check. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Other sources

LIBPNG has ARM NEON Palette Expansion Out-of-Bounds Read on AArch64

— Microsoft

LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. In versions 1.6.36 through 1.6.55, an out-of-bounds read and write exists in libpng's ARM/AArch64 Neon-optimized palette expansion path. When expanding 8-bit paletted rows to RGB or RGBA, the Neon loop processes a final partial chunk without verifying that enough input pixels remain. Because the implementation works backward from the end of the row, the final iteration dereferences pointers before the start of the row buffer (OOB read) and writes expanded pixel data to the same underflowed positions (OOB write). This is reachable via normal decoding of attacker-controlled PNG input if Neon is enabled. Version 1.6.56 fixes the issue.

— MITRE

Affected Software

17 affected componentsFixes available
libpng LIBPNG>=1.6.36<=1.6.55
Microsoft cbl2 libpng 1.6.55-1
Microsoft azl3 libpng 1.6.55-1
libpng LIBPNG>=1.6.36<1.6.56
IBM Netezza Software<=11.3.0.3-IF2
Google Android
All of the following
azurelinux/libpng<1.6.56-1
1.6.56-1
Microsoft Azure Linux=3.0
All of the following
azurelinux/libpng<1.6.56-1
1.6.56-1
Microsoft CBL-Mariner=2.0
android/platform/external/libpng>=17-next:0<17-next:2026-09-01
17-next:2026-09-01
android/platform/external/libpng>=15:0<15:2026-09-01
15:2026-09-01
android/platform/external/libpng>=16:0<16:2026-09-01
16:2026-09-01
android/platform/external/libpng>=16-qpr2:0<16-qpr2:2026-09-01
16-qpr2:2026-09-01
android/platform/external/libpng>=17:0<17:2026-09-01
17:2026-09-01
android/platform/external/libpng>=14:0<14:2026-09-01
14:2026-09-01
debian/libpng1.6
1.6.39-2+deb12u51.6.39-2+deb12u61.6.48-1+deb13u51.6.48-1+deb13u61.6.59-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade azurelinux/libpng to a version that resolves this vulnerability.

    Fixed in 1.6.56-1
  2. Upgrade

    Upgrade android/platform/external/libpng to a version that resolves this vulnerability.

    Fixed in 17-next:2026-09-01
  3. Upgrade

    Upgrade android/platform/external/libpng to a version that resolves this vulnerability.

    Fixed in 15:2026-09-01
  4. Upgrade

    Upgrade android/platform/external/libpng to a version that resolves this vulnerability.

    Fixed in 16:2026-09-01
  5. Upgrade

    Upgrade android/platform/external/libpng to a version that resolves this vulnerability.

    Fixed in 16-qpr2:2026-09-01
  6. Upgrade

    Upgrade android/platform/external/libpng to a version that resolves this vulnerability.

    Fixed in 17:2026-09-01
  7. Upgrade

    Upgrade android/platform/external/libpng to a version that resolves this vulnerability.

    Fixed in 14:2026-09-01
  8. Upgrade

    Upgrade debian/libpng1.6 to a version that resolves this vulnerability.

    Fixed in 1.6.39-2+deb12u5Fixed in 1.6.39-2+deb12u6Fixed in 1.6.48-1+deb13u5Fixed in 1.6.48-1+deb13u6Fixed in 1.6.59-1
  9. Upgrade

    Upgrade libpng to a version that resolves this vulnerability.

    Fixed in 1.6.56

Event History

Mar 26, 2026
CVE Published
via MITRE·04:51 PM
Data Sourced
via MITRE·04:51 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·06:03 PM
DescriptionSeverityAffected Software
Mar 29, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Aug 20, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Sep 1, 2026
Advisory Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
Affected Software
Sep 8, 2026
Data Sourced
via Android·12:00 AM
SeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2026-33636?

The severity of CVE-2026-33636 is considered to be high due to the potential for out-of-bounds reads and writes.

2

How do I fix CVE-2026-33636?

To fix CVE-2026-33636, update libpng to version 1.6.56 or later, as this version addresses the vulnerability.

3

What versions of libpng are affected by CVE-2026-33636?

CVE-2026-33636 affects libpng versions 1.6.36 through 1.6.55.

4

What are the implications of CVE-2026-33636?

The implications of CVE-2026-33636 include the risk of arbitrary code execution or application crashes due to out-of-bounds memory access.

5

Is CVE-2026-33636 only applicable to ARM architecture?

CVE-2026-33636 is primarily identified in the context of ARM architecture, specifically on AArch64 systems.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203