dompdf/dompdf security advisory
CVE-2026-59942: Dompdf: Denial of Service (DoS) via Resource Exhaustion using Oversized Image Bitmaps
CVE-2026-59942 is a medium-severity denial of service vulnerability in the PHP package dompdf/dompdf (CVSS 7.5), published 28 July 2026. It is fixed in 3.1.6; earlier versions are affected. It can be exploited without an account.
medium 7.5 published 2026-07-28 · updated 2026-08-04
- Affected versions
- < 3.1.6
- Fixed in
- 3.1.6
- Newest release
- 3.1.6
- Severity
- Medium · CVSS 7.5
- Type
- Denial of service
CWE-400 - Exploited in the wild
- Not on the CISA KEV list
checked 2026-11-04
Is your dompdf/dompdf version affected?
Who can exploit CVE-2026-59942
- Access: No account. Anyone who can send a request to an app that uses the affected code.
CVSS vector (scored by NVD): CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
How to fix CVE-2026-59942 in dompdf/dompdf
- Find the installed version:
composer show dompdf/dompdf. If you never required it yourself,composer why dompdf/dompdfshows which package pulls it in. - Update it:
composer update dompdf/dompdf --with-all-dependencies. You need 3.1.6 or newer. - If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example
"dompdf/dompdf": "^3.1.6"if you can take that version), or upgrade the package that requires it. - Run
composer audit. It reads the same advisory data and should no longer list CVE-2026-59942. - Commit composer.lock and deploy it. On the server, run
composer install --no-devfrom the lock file, notcomposer update.
If you cannot upgrade yet
- Rate-limit the affected endpoint and cap request body, header and upload sizes at the web server.
- If your app does not use the affected feature, note that in your audit, but still plan the upgrade.
The CVE-2026-59942 advisory
Dompdf is an HTML to PDF converter for PHP. Versions 3.15 and prior are vulnerable to a Denial of Service (DoS) attack via resource exhaustion. An attacker can crash the PHP process by providing a specially crafted HTML document containing a single image with massive dimensions (e.g., 30,000x30,000 pixels). While Dompdf implements internal checks to validate image dimensions, these can be bypassed by using a high-entropy image (such as random noise) encoded in Base64 and wrapped in specific CSS containers. The vulnerability exists because the dimension validation happens early, but the resource allocation for calculating the object's bounding box and internal buffers during the rendering phase does not strictly limit the cumulative CPU time or memory usage for a single object that has passed the initial check. An unauthenticated remote attacker can cause a complete Denial of Service on the web server by submitting a crafted HTML string. This affects any application that allows users to provide HTML content or URLs that are subsequently converted to PDF using Dompdf. This issue has been fixed in version 3.16.
References
- GitHub advisory GHSA-f5gf-2cj8-52g2 github.com
- Fix commit 7c65e7b github.com
- Fix commit 89164ea github.com
- Release v3.1.6 github.com
Other dompdf/dompdf advisories
- medium CVE-2026-59943: Dompdf: Embedded SVG images can leak existence of files and directories within the filesystem 2026-07-22
- medium CVE-2026-59941: Dompdf: Uncontrolled resource consumption based on declared BMP dimensions 2026-07-22
- medium CVE-2026-56722: Dompdf: Local file read due to improper file path validation in SVG images encoded as data-URI 2026-07-22
- low CVE-2026-55555: Dompdf: File existence oracle via font-face stylesheet declaration 2026-07-22
- low CVE-2026-55554: Dompdf: Chroot Validation Bypass 2026-07-22
- critical CVE-2021-3902: Improper Restriction of XML External Entity Reference in dompdf/dompdf 2024-11-15
Related
Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.
Ask about a fixWhere this data comes from
- Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data
composer audituses. Synced 2026-11-03. - Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
- Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.