Approved changes feed: RSS · Atom
cpe:2.3:a:libpng:libpng:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Libpng (b87086c8-9966-53f7-b270-df72ee4b8d73) |
|---|---|
| Product | Libpng (8c2111f0-4992-59d8-8db9-d4f954eb189a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/glennrp/libpng |
purl2cpe | 2026-06-01 10:15:48.895521 |
pkg:sourceforge/libpng |
purl2cpe | 2026-06-01 10:15:48.895523 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-3713 |
vulnerable | 2026-06-08 08:01:19.226371 |
pnggroup libpng pnm2png pnm2png.c do_pnm2png heap-based overflow
MEDIUM (5.3)
A flaw has been found in pnggroup libpng up to 1.6.55. Affected by this vulnerability is the function do_pnm2png of the file contrib/pngminus/pnm2png.c of the component pnm2png. This manipulation of the argument width/height causes heap-based buffer overflow. The attack is restricted to local execution. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.
Published: 2026-03-08T06:02:11.204Z
Updated: 2026-03-11T13:43:22.092Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-34757 |
vulnerable | 2026-06-08 07:59:13.075386 |
LIBPNG has a yse-after-free in png_set_PLTE, png_set_tRNS and png_set_hIST leading to corrupted chunk data and potential heap information disclosure
MEDIUM (5.1)
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.0.9 to before 1.6.57, passing a pointer obtained from png_get_PLTE, png_get_tRNS, or png_get_hIST back into the corresponding setter on the same png_struct/png_info pair causes the setter to read from freed memory and copy its contents into the replacement buffer. The setter frees the internal buffer before copying from the caller-supplied pointer, which now dangles. The freed region may contain stale data (producing silently corrupted chunk metadata) or data from subsequent heap allocations (leaking unrelated heap contents into the chunk struct). This vulnerability is fixed in 1.6.57.
Published: 2026-04-09T14:41:18.195Z
Updated: 2026-05-09T10:21:48.394Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33636 |
vulnerable | 2026-06-08 07:59:10.521241 |
LIBPNG has ARM NEON Palette Expansion Out-of-Bounds Read on AArch64
HIGH (7.6)
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.
Published: 2026-03-26T16:51:58.289Z
Updated: 2026-03-26T18:45:26.631Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33416 |
vulnerable | 2026-06-08 07:59:09.915265 |
LIBPNG has use-after-free via pointer aliasing in `png_set_tRNS` and `png_set_PLTE`
HIGH (7.5)
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.
Published: 2026-03-26T16:48:54.174Z
Updated: 2026-04-01T03:55:17.603Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25646 |
vulnerable | 2026-06-08 07:53:20.150675 |
LIBPNG has a heap buffer overflow in png_set_quantize
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 specification. This vulnerability is fixed in 1.6.55.
Published: 2026-02-10T17:04:38.501Z
Updated: 2026-09-01T12:04:57.909Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22801 |
vulnerable | 2026-06-08 07:51:13.952831 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22695 |
vulnerable | 2026-06-08 07:51:13.621006 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-66293 |
vulnerable | 2026-06-08 07:41:18.554409 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-65018 |
vulnerable | 2026-06-08 07:39:20.635851 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-64720 |
vulnerable | 2026-06-08 07:39:20.195070 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-64506 |
vulnerable | 2026-06-08 07:39:19.866914 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-64505 |
vulnerable | 2026-06-08 07:39:19.866459 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-28164 |
vulnerable | 2026-06-08 07:14:56.029478 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-28162 |
vulnerable | 2026-06-08 07:14:56.028974 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-7317 |
vulnerable | 2026-06-08 05:14:14.258532 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-12652 |
vulnerable | 2026-06-08 05:08:47.443399 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-3751 |
vulnerable | 2026-06-08 05:07:46.006279 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2015-8126 |
vulnerable | 2026-06-08 05:07:03.241105 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2015-0973 |
vulnerable | 2026-06-08 05:06:24.409926 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2013-7354 |
vulnerable | 2026-06-08 05:05:10.135149 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2013-7353 |
vulnerable | 2026-06-08 05:05:10.121329 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2011-3045 |
vulnerable | 2026-06-08 04:58:10.351730 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2011-2692 |
vulnerable | 2026-06-08 04:58:08.414532 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2011-2691 |
vulnerable | 2026-06-08 04:58:08.413750 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2011-2690 |
vulnerable | 2026-06-08 04:58:08.413036 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2011-2501 |
vulnerable | 2026-06-08 04:58:07.266687 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2010-2249 |
vulnerable | 2026-06-08 04:55:06.011642 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2010-1205 |
vulnerable | 2026-06-08 04:54:06.385549 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2010-0205 |
vulnerable | 2026-06-08 04:51:53.510457 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2009-5063 |
vulnerable | 2026-06-08 04:51:51.871367 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2009-2042 |
vulnerable | 2026-06-08 04:51:26.175583 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2009-0040 |
vulnerable | 2026-06-08 04:51:07.204407 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2008-5907 |
vulnerable | 2026-06-08 04:50:53.555157 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2008-3964 |
vulnerable | 2026-06-08 04:50:37.346980 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2007-5269 |
vulnerable | 2026-06-08 04:50:04.755551 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2007-5268 |
vulnerable | 2026-06-08 04:50:04.752022 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2007-5267 |
vulnerable | 2026-06-08 04:50:04.751118 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2007-5266 |
vulnerable | 2026-06-08 04:50:04.750409 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.