CVE-2026-33416

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
60.5%
KEV
Not listed

Published

March 26, 2026

Last Modified

April 2, 2026

Advisory Details (6)

Auto-updated Jun 10, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

Use-after-free via pointer aliasing in `png_set_tRNS` and `png_set_PLTE` · Advisory · pnggroup/libpng · GitHub

https://github.com/pnggroup/libpng/security/advisories/GHSA-m4pc-p4q3-4c7j
github_pr

fix: resolve use-after-free on png_ptr->trans_alpha

Upstream fix in progress (PR #824 · pnggroup/libpng, state=closed)

https://github.com/pnggroup/libpng/pull/824
github_commit

commit c1b0318b393c (pnggroup/libpng)

Fix landed in pnggroup/libpng commit c1b0318b393c — awaiting tagged release

https://github.com/pnggroup/libpng/commit/c1b0318b393c90679e6fa5bc1d329fd5d5012ec1
github_commit

commit a3a21443ed12 (pnggroup/libpng)

Fix landed in pnggroup/libpng commit a3a21443ed12 — awaiting tagged release

https://github.com/pnggroup/libpng/commit/a3a21443ed12bfa1ef46fa0d4fb2b74a0fa34a25
github_commit

commit 7ea9eea884a2 (pnggroup/libpng)

Fix landed in pnggroup/libpng commit 7ea9eea884a2 — awaiting tagged release

https://github.com/pnggroup/libpng/commit/7ea9eea884a2328cc7fdcb3c0c00246a50d90667
github_commit

commit 23019269764e (pnggroup/libpng)

Fix landed in pnggroup/libpng commit 23019269764e — awaiting tagged release

https://github.com/pnggroup/libpng/commit/23019269764e35ed8458e517f1897bd3c54820eb

Vendor Advisories for CVE-2026-33416(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhaiis/model-opt-cuda-rhel9:17806819842026-06-10redhat
redhatlibpng-2:1.6.37-12.el9_4.42026-05-26redhat
redhatlibpng-2:1.6.40-8.el10_0.42026-05-26redhat
redhatlibpng-2:1.6.37-12.el9_2.42026-05-26redhat
redhatlibpng-2:1.6.37-12.el9_6.42026-05-26redhat
redhatlibpng-2:1.6.40-8.el10_1.42026-05-18redhat
redhatlibpng-2:1.6.37-12.el9_7.42026-05-18redhat
redhatthunderbird-0:140.9.1-1.el8_62026-05-11redhat
redhatfirefox-0:140.9.1-2.el7_92026-05-06redhat
redhatfirefox-0:140.9.1-1.el9_22026-05-06redhat
redhatthunderbird-0:140.9.1-1.el8_42026-05-06redhat
redhatthunderbird-0:140.9.1-1.el8_82026-05-06redhat
redhatfirefox-0:140.9.1-1.el8_62026-05-05redhat
redhatfirefox-0:140.9.1-1.el8_42026-05-05redhat
redhatfirefox-0:140.9.1-1.el8_82026-05-05redhat
redhatfirefox-0:140.9.1-1.el9_42026-05-05redhat
redhatfirefox-0:140.9.1-1.el9_62026-05-05redhat
redhatfirefox-0:140.9.1-1.el10_02026-05-05redhat
redhatfirefox-0:140.9.1-1.el9_02026-05-05redhat
redhatthunderbird-0:140.9.1-1.el9_22026-05-04redhat
redhatthunderbird-0:140.9.1-1.el9_62026-05-04redhat
redhatthunderbird-0:140.9.1-1.el9_42026-05-04redhat
redhatthunderbird-0:140.9.1-1.el9_02026-04-30redhat
redhatthunderbird-0:140.9.1-1.el10_02026-04-29redhat
redhatfirefox-0:140.9.1-1.el8_22026-04-29redhat
redhatjava-25-openjdk-1:25.0.3.0.9-1.el92026-04-22redhat
redhatthunderbird-0:140.9.1-1.el10_12026-04-22redhat
redhatjava-11-openjdk-portable2026-04-22redhat
redhatjava-11-openjdk-1:11.0.31.0.11-1.el92026-04-22redhat
redhatthunderbird-0:140.9.1-1.el8_102026-04-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Additional Vendor Advisories

(22)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 108 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-08 15:15 UTCEPSS rescore
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-01 15:06 UTCEPSS rescore
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 03:32 UTCOSV refresh
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 75 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-27 03:08 UTCEPSS rescore
  4. 2026-06-25 13:49 UTCEPSS rescore
  5. 2026-06-25 13:49 UTCEPSS rescore
  6. 2026-06-24 14:05 UTCEPSS rescore
  7. 2026-06-23 21:33 UTCEPSS rescore
  8. 2026-06-23 21:33 UTCEPSS rescore
  9. 2026-06-22 14:25 UTCEPSS rescore
  10. 2026-06-22 14:25 UTCEPSS rescore
  11. 2026-06-21 14:56 UTCEPSS rescore
  12. 2026-06-21 14:56 UTCEPSS rescore
  13. 2026-06-21 01:59 UTCEPSS rescore
  14. 2026-06-19 19:25 UTCEPSS rescore
  15. 2026-06-19 19:25 UTCEPSS rescore
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-18 17:52 UTCEPSS rescore
  18. 2026-06-17 17:53 UTCEPSS rescore
  19. 2026-06-16 17:52 UTCEPSS rescore
  20. 2026-06-15 17:49 UTCEPSS rescore
  21. 2026-06-14 23:18 UTCEPSS rescore
  22. 2026-06-13 23:00 UTCEPSS rescore
  23. 2026-06-12 23:12 UTCEPSS rescore
  24. 2026-06-12 23:12 UTCEPSS rescore
  25. 2026-06-11 23:20 UTCEG score recompute
  26. 2026-06-11 23:20 UTCVendor advisory
  27. 2026-06-11 14:00 UTCEPSS rescore
  28. 2026-06-10 22:18 UTCEPSS rescore
  29. 2026-06-10 16:39 UTCEG score recompute
  30. 2026-06-10 16:39 UTCVendor advisory
  31. 2026-06-10 13:22 UTCEPSS rescore
  32. 2026-06-10 04:06 UTCEG score recompute
  33. 2026-06-10 04:06 UTCVendor advisory
  34. 2026-06-09 15:31 UTCEG score recompute
  35. 2026-06-09 15:31 UTCVendor advisory
  36. 2026-06-08 14:17 UTCEPSS rescore
  37. 2026-06-08 14:17 UTCEPSS rescore
  38. 2026-06-08 13:23 UTCEG score recompute
  39. 2026-06-08 13:23 UTCVendor advisory
  40. 2026-06-08 00:53 UTCEG score recompute
  41. 2026-06-08 00:53 UTCVendor advisory
  42. 2026-06-07 15:25 UTCEPSS rescore
  43. 2026-06-07 15:25 UTCEPSS rescore
  44. 2026-06-07 15:25 UTCEPSS rescore
  45. 2026-06-07 12:03 UTCEG score recompute
  46. 2026-06-07 12:03 UTCVendor advisory
  47. 2026-06-06 13:47 UTCEPSS rescore
  48. 2026-06-06 13:47 UTCEPSS rescore
  49. 2026-06-05 22:47 UTCEPSS rescore
  50. 2026-06-05 22:47 UTCEPSS rescore
  51. 2026-06-05 06:10 UTCEPSS rescore
  52. 2026-06-05 06:10 UTCEPSS rescore
  53. 2026-06-04 13:12 UTCEPSS rescore
  54. 2026-06-04 13:12 UTCEPSS rescore
  55. 2026-06-02 20:13 UTCEPSS rescore
  56. 2026-06-01 13:52 UTCEPSS rescore
  57. 2026-06-01 13:52 UTCEPSS rescore
  58. 2026-06-01 13:51 UTCEPSS rescore
  59. 2026-06-01 06:13 UTCOSV refresh
  60. 2026-05-31 22:30 UTCEPSS rescore
  61. 2026-05-31 22:30 UTCEPSS rescore
  62. 2026-05-31 00:16 UTCEPSS rescore
  63. 2026-05-31 00:16 UTCEPSS rescore
  64. 2026-05-31 00:16 UTCEPSS rescore
  65. 2026-05-29 13:44 UTCEPSS rescore
  66. 2026-05-29 13:44 UTCEPSS rescore
  67. 2026-05-28 13:44 UTCEPSS rescore
  68. 2026-05-28 13:44 UTCEPSS rescore
  69. 2026-05-28 13:44 UTCEPSS rescore
  70. 2026-05-27 13:40 UTCEPSS rescore
  71. 2026-05-27 13:40 UTCEPSS rescore
  72. 2026-05-27 13:40 UTCEPSS rescore
  73. 2026-05-26 13:44 UTCEPSS rescore
  74. 2026-05-26 07:18 UTCEPSS rescore
  75. 2026-05-26 07:18 UTCEPSS rescore

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-33416?
CVE-2026-33416 is a high vulnerability published on March 26, 2026. 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, pngsettRNS and pngsetPLTE each alias a heap-allocated buffer between pngstruct and pnginfo, sharing a single allocation…
When was CVE-2026-33416 disclosed?
CVE-2026-33416 was first published in the National Vulnerability Database on March 26, 2026, with the most recent update on April 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33416 actively exploited?
CVE-2026-33416 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 60.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-33416?
CVE-2026-33416 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-33416?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33416, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-33416

Explore →

Is Your Infrastructure Affected by CVE-2026-33416?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs