Is dompdf/dompdf 3.0 vulnerable?
Composer · 3 releases from 3.0.0 to 3.0.2 · latest dompdf/dompdf is 3.1.6 · checked 1 Nov 2026
Yes: 6 known advisories
Yes. dompdf/dompdf 3.0.2, the last 3.0 release, is affected by 6 known security advisories (4 medium, 2 low), including CVE-2026-59943, CVE-2026-59942, CVE-2026-59941. Upgrade to 3.1.6 or later to fix all of them.
composer require dompdf/dompdf:^3.1.6Advisories affecting dompdf/dompdf 3.0.2
Dompdf: Embedded SVG images can leak existence of files and directories within the filesystem
- Affected
- <3.1.6
- Fixed in
- 3.1.6
Dompdf: Denial of Service (DoS) via Resource Exhaustion using Oversized Image Bitmaps
- Affected
- <3.1.6
- Fixed in
- 3.1.6
Dompdf: Uncontrolled resource consumption based on declared BMP dimensions
- Affected
- <3.1.6
- Fixed in
- 3.1.6
Dompdf: Local file read due to improper file path validation in SVG images encoded as data-URI
- Affected
- <3.1.6
- Fixed in
- 3.1.6
Dompdf: File existence oracle via font-face stylesheet declaration
- Affected
- <3.1.6
- Fixed in
- 3.1.6
Dompdf: Chroot Validation Bypass
- Affected
- <3.1.6
- Fixed in
- 3.1.6
Which of your client projects are still on dompdf/dompdf 3.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact dompdf/dompdf version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other dompdf/dompdf versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.