On this page (7 sections)

Ubuntu published USN-9082-1 on 12 November 2026. It covers pngquant, a command-line utility that optimizes PNG images, and describes a buffer overflow triggered by a specially crafted PNG file. Ubuntu says the result could be a crash or the execution of arbitrary code.

If you run Ubuntu 16.04 LTS servers that use pngquant to process images, for example in a build pipeline, an upload workflow or a media optimization script, this notice is relevant to you. Everyone else can treat it as a short check.

What happened

The notice credits Choi Jaeseung with discovering that pngquant incorrectly handled certain PNG images, which leads to a buffer overflow. Ubuntu's summary says the tool could be made to crash or run programs as your login if it opened a specially crafted file. The notice lists one CVE, CVE-2016-5735.

The fixed package version is published with an esm1 suffix, which indicates Ubuntu's Extended Security Maintenance. The notice also mentions Ubuntu Pro, which Ubuntu describes as providing ten-year security coverage for 25,000+ packages and as free for up to five machines.

This story rests on a single source, the Ubuntu notice itself. It gives no CVSS score, no exploit details and no statement about attacks in the wild, so none are claimed here.

Understanding the weakness

A buffer overflow happens when a program writes more data into a memory area than it was sized to hold. With image tools, the input is the image file itself: a malformed PNG can describe dimensions or data the code does not handle safely. The usual outcomes are a crash or, in worse cases, an attacker steering the program into running their own code with the privileges of the user that launched it.

That last point matters for how you assess risk. The danger depends on who can hand a PNG to pngquant and which account runs it. A tool run by hand on images you created yourself is a very different situation from a service that optimizes files uploaded by strangers.

Who is realistically exposed

  • Servers on Ubuntu 16.04 LTS with the pngquant package installed.
  • Web applications, CMS plugins or scripts that call pngquant on user-supplied or third-party images.
  • Build and deployment machines that compress images fetched from external sources.
  • Shared hosting or agency servers where several sites may feed images to the same tool.

The notice only lists Ubuntu 16.04 LTS. It does not say anything about other Ubuntu releases or other distributions, so do not assume either way. Check your own vendor's advisories if you run something else.

How to check your exposure

First confirm whether pngquant is installed and which version you have. This read-only command prints the installed package status on Ubuntu; look for a version older than 2.5.0-1ubuntu0.1~esm1.

Show the installed pngquant package and version (Ubuntu 16.04)Shell
dpkg -l pngquant

If you want to see whether any code on the server calls pngquant, search your application and script directories. This read-only search lists files that mention it; adjust the paths to where your sites live.

Find scripts and configs that reference pngquant (run on the server)Shell
grep -rIl pngquant /var/www /etc 2>/dev/null

What to do now

  1. Run dpkg -l pngquant on each Ubuntu 16.04 LTS host and note which ones have it installed.
  2. Update the package with a standard system update (command below) so you reach 2.5.0-1ubuntu0.1~esm1 or later.
  3. If the update does not offer that version, check how your 16.04 systems receive ESM updates, since the fix is published as an esm1 build.
  4. Confirm the new version with dpkg -l pngquant after updating.
  5. Until patched, avoid running pngquant on PNG files from untrusted sources, and run it under a low-privilege account.
  6. If pngquant is no longer needed, remove it from servers that do not use it.

Ubuntu says a standard system update makes the necessary changes. This updates package lists and then upgrades only pngquant on a host that already has it installed.

Update only the pngquant package (Ubuntu 16.04 LTS)Shell
sudo apt update && sudo apt install --only-upgrade pngquant

Detection and monitoring afterwards

A buffer overflow that only crashes the tool can show up as repeated failures in image-processing jobs. Watch your application logs and job queues for pngquant exiting abnormally, and check system logs for crash messages tied to it. This read-only search looks through the system log for pngquant lines mentioning a crash or error; the log path may differ on your setup.

Look for pngquant crashes in the system log (run on the server)Shell
grep -i pngquant /var/log/syslog | grep -i -E 'segfault|killed|error'

If a crash coincides with a particular uploaded file, keep the file for analysis and review what else that account did around the same time. For the broader picture of what to do if you suspect compromise, see Website hacked: what to do and Check if a website is hacked. For general habits that reduce exposure, see Small business website security.

For a regular outside view of your sites, Webforta Monitor can watch uptime, certificates and DNS, though it does not patch or inspect server packages such as pngquant.

Timeline

Date from the Ubuntu notice
DateEvent
12 November 2026Ubuntu publishes USN-9082-1 for pngquant on 16.04 LTS

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. USN-9082-1: pngquant vulnerability | Ubuntu security notices | Ubuntuubuntu.com ·
  • Ubuntu
  • USN
  • pngquant
  • buffer overflow
  • image processing