Libpng vulnerabilitiesNone on the known-exploited list.

Vendor
The short answer

Libpng has 47 published vulnerabilities across 3 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Libpng, with 45. If you run Libpng software, patch the exploited flaws first.

See the exploited flaws

We keep watching the known-exploited list.

Products

Which Libpng products have the most vulnerabilities?

Libpng leads with 45 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.

  1. Libpng45
  2. Pngcheck2
  3. Libgpng0
Published vulnerabilities
Known exploited

Which Libpng vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Libpng's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Libpng flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 43%

    Buffer overflow in pngpread.c in libpng before 1.2.44 and 1.4.x before 1.4.3, as used in progressive applications, might allow remote attackers to execute arbitrary code via a PNG image that triggers an additional...

    CVSS9.8Published30 Jun 2010
  2. 10%

    Multiple buffer overflows in the (1) png_set_PLTE and (2) png_get_PLTE functions in libpng before 1.0.64, 1.1.x and 1.2.x before 1.2.54, 1.3.x and 1.4.x before 1.4.17, 1.5.x before 1.5.24, and 1.6.x before 1.6.19...

    CVSS7.5Published13 Nov 2015
  3. 9.4%

    png_image_free in png.c in libpng 1.6.x before 1.6.37 has a use-after-free because png_image_free_function is called under png_safe_execute.

    CVSS5.3Published4 Feb 2019
  4. 6.5%

    The png_set_text_2 function in pngset.c in libpng 1.0.x before 1.0.59, 1.2.x before 1.2.49, 1.4.x before 1.4.11, and 1.5.x before 1.5.10 allows remote attackers to cause a denial of service (crash) or execute...

    CVSS6.8Published29 May 2012
  5. 6.5%

    Integer underflow in the png_check_keyword function in pngwutil.c in libpng 0.90 through 0.99, 1.0.x before 1.0.66, 1.1.x and 1.2.x before 1.2.56, 1.3.x and 1.4.x before 1.4.19, and 1.5.x before 1.5.26 allows remote...

    CVSS8.8Published14 Apr 2016
  6. 6.4%

    The png_convert_to_rfc1123 function in png.c in libpng 1.0.x before 1.0.64, 1.2.x before 1.2.54, and 1.4.x before 1.4.17 allows remote attackers to obtain sensitive process memory information via crafted tIME chunk...

    CVSS5.0Published24 Nov 2015
  7. 6.1%

    Buffer overflow in the png_set_PLTE function in libpng before 1.0.65, 1.1.x and 1.2.x before 1.2.55, 1.3.x, 1.4.x before 1.4.18, 1.5.x before 1.5.25, and 1.6.x before 1.6.20 allows remote attackers to cause a denial...

    CVSS7.3Published21 Jan 2016
  8. 5.6%

    pngrtran.c in libpng 1.5.x before 1.5.1 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted palette-based PNG image that triggers a buffer...

    CVSS6.8Published18 Jan 2011
  9. 5.5%

    libpng 1.0.6 through 1.0.32, 1.2.0 through 1.2.26, and 1.4.0beta01 through 1.4.0beta19 allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a PNG file with...

    CVSS7.5Published14 Apr 2008
  10. 5.1%

    The png_set_text_2 function in libpng 0.71 before 1.0.67, 1.2.x before 1.2.57, 1.4.x before 1.4.20, 1.5.x before 1.5.28, and 1.6.x before 1.6.27 allows context-dependent attackers to cause a NULL pointer dereference...

    CVSS7.5Published30 Jan 2017
Every product

All Libpng products we track.

3 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.

Precursor Intelligence

Running Libpng? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

Our catalogue lists 47 published vulnerabilities across 3 products and 342 versions from Libpng.

None of Libpng's vulnerabilities is on the list of flaws known to be exploited today.

Libpng, with 45 published vulnerabilities. Its own page lists the ones known to be exploited.

Create a Precursor Intelligence account and track the Libpng products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.