On this page (7 sections)

On November 20, 2026, the Debian security team published DSA-6645-1, an update for libgd2, the library many applications use to create and manipulate images. Debian says multiple vulnerabilities were found that could result in denial of service or information leaks.

If you run Debian 13 (trixie) servers that host websites, especially PHP sites that use image processing, you should check your libgd2 package version and update. The advisory is short, so this article also covers what is not yet known.

What Debian announced

The advisory was sent by Salvatore Bonaccorso to the Debian security announcement list. It describes libgd2 as a library for programmatic graphics creation and manipulation and states that multiple vulnerabilities were discovered. For the stable distribution (trixie), the problems are fixed in version 2.3.3-14~deb13u3, and Debian recommends upgrading libgd2 packages. A Debian bug, 1153907, is referenced, and the advisory points readers to the Debian security tracker page for libgd2 for detailed status.

Only this one primary source is available so far. Other outlets have not yet published independent analysis, so everything below about the issue itself comes from Debian's short notice.

What we do not know yet

The advisory lists the CVE ID as not yet available. That means we cannot say how many distinct flaws are involved, how severe each one is, or which image formats or functions are affected. Debian does not say whether the bugs are reachable remotely, whether any require a crafted image, or whether anyone is exploiting them.

  • No CVE identifiers or CVSS scores have been published in the source material.
  • No technical root cause (for example, which parser or function) is described.
  • No exploitation status is given, so treat it as unconfirmed rather than assuming either way.
  • Only trixie is named as fixed. Other Debian releases are not mentioned in the advisory; check the Debian security tracker for libgd2 for their status.

We will not speculate beyond that. Debian's own description of the impact, denial of service or information leaks, is the extent of what is confirmed.

Why libgd2 matters for website owners

Libraries like libgd2 sit underneath other software. A web application, a PHP extension or a command-line tool may link against it to resize, convert or draw images. Many sites process images that users upload or that come from third parties, such as avatars, product photos or generated charts. When an image library has memory-handling or parsing bugs, the usual consequences are a crashed process (denial of service) or exposure of memory contents (information leak). Debian's wording matches those two outcomes, though it does not give details of how they occur here.

Whether your site is exposed depends on whether libgd2 is installed and whether anything on the server actually uses it. A server with the package present but unused is lower risk than one that processes untrusted images, but updating is cheap either way.

How to check if you are affected

Run this on a Debian server to list installed packages whose names start with libgd and their versions. On trixie, compare the version shown to 2.3.3-14~deb13u3; the exact binary package names can differ, so the wildcard catches anything starting with libgd.

List installed libgd packages and versions (Debian)Shell
dpkg -l 'libgd*'

To see whether an upgrade is pending for the packages you found, this read-only command lists upgradable packages and filters for libgd. If a libgd line appears, an update is available from your configured repositories; no output means none is pending.

Check for pending libgd upgrades (Debian)Shell
apt list --upgradable 2>/dev/null | grep -i libgd

If you use PHP, check whether the GD extension is loaded, since PHP's GD support is a typical way web apps reach this library. This command prints gd if the extension is enabled for the command-line PHP. Your web server's PHP-FPM or Apache module may use a different configuration, so check that too.

Check whether PHP has the GD extension loadedShell
php -m | grep -i '^gd$'

What to do now

  1. Identify Debian 13 (trixie) servers and containers that have libgd packages installed, using the dpkg listing above.
  2. Refresh package lists and upgrade the libgd packages to 2.3.3-14~deb13u3 or later.
  3. Restart services that load the library, such as PHP-FPM or your web server, so running processes use the patched code.
  4. Rebuild and redeploy container images that are based on Debian trixie and include libgd, since running containers do not pick up host updates.
  5. Check the Debian security tracker page for libgd2 if you run another Debian release, and apply whatever fix it lists.
  6. Review web server and application logs for unusual crashes or repeated restarts around image-handling endpoints.

This updates only the libgd packages on a Debian system. Run it from a shell with root privileges or via sudo.

Update package lists and upgrade libgd packages (Debian)Shell
sudo apt-get update
sudo apt-get install --only-upgrade 'libgd*'
Caution. Restarting PHP-FPM or the web server briefly interrupts requests. Do it in a maintenance window on busy sites, and confirm the service name on your system first (for example, the PHP-FPM unit name includes the PHP version).

After updating, run the dpkg listing again and confirm the version is 2.3.3-14~deb13u3 or newer on trixie.

Detection and monitoring afterwards

Because the advisory gives no indicators of compromise and no exploitation details, there is nothing specific to hunt for. Practical monitoring is general: watch for unexpected crashes in your PHP or image-processing workers, spikes in resource use after image uploads, and unplanned changes to files on the server. If you suspect something odd, the guide on checking if a website is hacked walks through the basics.

For ongoing hygiene, keep automatic security updates enabled where your change process allows it, and subscribe to the Debian security announcement list so you hear about advisories like this one quickly. The same release batch includes neighboring notices, DSA-6644-1 for ruby3.3 and DSA-6646-1 for gpgme1.0, which may also apply to your servers.

If you manage several sites, uptime monitoring can help you notice if a patch or restart causes an unexpected outage.

Timeline

Known events from the Debian advisory
DateEvent
November 20, 2026Debian publishes DSA-6645-1 for libgd2, with fixed version 2.3.3-14~deb13u3 for trixie

The available source material contains no CVE identifiers, CVSS scores or exploitation reports. This is a developing story: once CVE identifiers and severity ratings are published, the picture of how urgent this is should become clearer.

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. [SECURITY] [DSA 6645-1] libgd2 security updatelists.debian.org ·
  • Debian
  • libgd2
  • DSA
  • PHP GD
  • patching