Skip to main content
Mallory
UnratedVulnerability

CVE-2026-9672: Buffer Overflow in libgd GIF Decoding

Updated 9 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days6 mentions · peak 3 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
PHP Group
IdentifiersCVE-2026-9672CWE-120

CVE-2026-9672 is a buffer overflow vulnerability in the GD Graphics Library (libgd) triggered by decoding a specially crafted GIF image. The defect involves LZW decompression during GIF handling; associated fixes also address use of uninitialized memory. Applications that process attacker-controlled GIF images through an affected library may suffer denial of service or potentially arbitrary code execution. Affected packages are covered by security updates for Debian and multiple Red Hat Enterprise Linux, Oracle Linux, AlmaLinux, Rocky Linux, and CentOS releases.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Processing a malicious GIF image can cause memory corruption, denial of service, and potentially arbitrary code execution in the affected application's security context. The CVSS v3.0 assessment is 8.1 (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), reflecting potentially high confidentiality, integrity, and availability impacts. Arbitrary code execution is a potential consequence, not an established exploitation outcome.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid processing untrusted GIF images through affected libgd installations, including GIF uploads and automated image-processing inputs. No specific vendor workaround is identified; exposure reduction does not replace installing the security update.

Remediation

Patch, then assume compromise.

Install the applicable vendor security update for libgd and its affected packages, including gd, gd-devel, and gd-progs where applicable. Fixed builds include Debian trixie libgd2 2.3.3-14~deb13u1; RHEL 9 gd 2.3.2-3.el9_8.1; RHEL 10 gd 2.3.3-20.el10_2.1; and RHEL 8.4, 8.6, and 8.8 gd builds 2.2.5-7.el8_4.1, 2.2.5-7.el8_6.1, and 2.2.5-7.el8_8.1, respectively. Oracle Linux 9 and 10 identify fixed releases 2.3.2-3.1 and 2.3.3-20.1, respectively. For other affected distribution streams, apply the corresponding Red Hat, AlmaLinux, or TuxCare advisory update. Use the package appropriate to the installed distribution and support stream rather than comparing upstream version numbers alone.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
PHP GroupPhpapplication
FAQ

Frequently asked questions

Is CVE-2026-9672 exploited in the wild?
As of Nov 13, 2026, Mallory has no reports of CVE-2026-9672 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-9672?
As of Nov 13, 2026, Mallory has found no public exploit for CVE-2026-9672.
Is there a patch for CVE-2026-9672?
Install the applicable vendor security update for libgd and its affected packages, including gd, gd-devel, and gd-progs where applicable. Fixed builds include Debian trixie libgd2 2.3.3-14~deb13u1; RHEL 9 gd 2.3.2-3.el9_8.1; RHEL 10 gd 2.3.3-20.el10_2.1; and RHEL 8.4, 8.6, and 8.8 gd builds 2.2.5-7.el8_4.1, 2.2.5-7.el8_6.1, and 2.2.5-7.el8_8.1, respectively.
What products are affected by CVE-2026-9672?
PHP Group Php.
Activity feed

Recent activity

49 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 12, 2026RHEL 7 : gd (RHSA-2026:98418) | Tenable®A buffer overflow in libgd triggered by processing a specially crafted GIF file affects the RHEL 7 gd packages. The advisory rates the issue Important, with potential high confidentiality, integrity, and availability impacts. Nessus identifies affected installations using self-reported package versions rather than testing exploitation. A security update is available under RHSA-2026:98418.Read more ↗tenable nessus pluginsNews · Nov 9, 2026CentOS Linux 7 [TuxCare] Security Update: gd / gd-devel / gd-p... | Tenable®A buffer-overflow vulnerability in LibGD triggered by processing a specially crafted GIF file. Affected CentOS Linux 7 packages are addressed by TuxCare advisory CENTOS7:CLSA-2026:1793782708, with patches published November 4, 2026. Nessus relies on reported package versions rather than directly testing the flaw. Exploit availability is reported for the combined plugin, without explicitly identifying which listed CVE has an exploit.Read more ↗tenable nessus pluginsNews · Nov 9, 2026RHEL 6 : gd (RHSA-2026:96206) | Tenable®A buffer overflow in libgd triggered by processing a specially crafted GIF file affects gd packages on Red Hat Enterprise Linux 6. The advisory assigns a CVSS v3 base score of 8.1, indicating high potential confidentiality, integrity, and availability impacts. Nessus identifies affected installations using self-reported version information rather than testing exploitation. A security update is available under RHSA-2026:96206.Read more ↗tenable nessus pluginsNews · Nov 5, 2026AlmaLinux 9.2 [TuxCare] Security Update: gd / gd-devel / gd-pr... | Tenable®A buffer overflow in libgd triggered by processing a specially crafted GIF file. The advisory identifies affected gd, gd-devel, and gd-progs packages on AlmaLinux 9.2. Nessus rates the vulnerability High, with a CVSS v3 base score of 8.1, and detects affected installations using self-reported package versions rather than exploitation testing.Read more ↗
+39 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.