Home / Security / Advisories / NTAP-20261016-0004
NTAP-20261016-0004 — CVE-2026-33416 LIBPNG Vulnerability in NetApp Products
Published 2026-10-16 · Updated 2026-10-16 · Status: Interim · Exploitation: Public · Severity: HIGH 7.5 · ONTAP affected: No — other NetApp product
Product family: NetApp Console / BlueXP · SolidFire / NetApp HCI | other NetApp product | highest CVSS: 7.5
CVEs in this advisory
- CVE-2026-33416 — HIGH · CVSS 7.5 · site index
What the CVE records say
CVE-2026-33416 — LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. In versions 1.2.1 through 1.6.55, `png_set_tRNS` and `png_set_PLTE` each alias a heap-allocated buffer between `png_struct` and `png_info`, sharing a single allocation across two structs with independent lifetimes. The `trans_alpha` aliasing has been present since at least libpng 1.0, and the `palette` aliasing since at least 1.2.1. Both affect all prior release lines `png_set_tRNS` sets `png_ptr->trans_alpha = info_ptr->trans_alpha` (256-byte buffer) and `png_set_PLTE` sets `info_ptr->palette = png_ptr->palette` (768-byte buffer). In both cases, calling `png_free_data` (with `PNG_FREE_TRNS` or `PNG_FREE_PLTE`) frees the buffer through `info_ptr` while the corresponding `png_ptr` pointer remains dangling. Subsequent row-transform functions dereference and, in some code paths, write to the freed memory. A second call to `png_set_tRNS` or `png_set_PLTE` has the same effect, because both functions call `png_free_data` internally before reallocating the `info_ptr` buffer. Version 1.6.56 fixes the issue.
Impact
Successful exploitation of this vulnerability could lead to disclosure of sensitive information, addition or modification of data, or Denial of Service (DoS).
Affected products
- NetApp Console Agent Container (docker_occm)
- NetApp Console Agent OVA
- NetApp SolidFire & HCI Management Node
- iNetApp SolidFire & HCI Storage Node (Element Software)
References
What to do
- Compare your installed product and version against the affected list above and the official advisory's affected-versions table.
- Apply the fixed release named in the official advisory, or the documented workaround if no fix ships yet.
- Limit management-plane exposure (BMC/management interfaces, web UIs, SNMP) until patched.
- Track follow-ups in the site CVE index and the security RSS feed.
Related reading
- Site CVE index — every CVE we track, split by year
- Security hub — recent NetApp advisories and what changed
- Security hardening baseline — applies to NetApp management planes generally
- Every NetApp advisory published in 2026