Dompdf: Embedded SVG images can leak existence of files and directories within the filesystem

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-59943: 0.42% estimated exploitation activity in the next 30 days; percentile 36.71 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. PoC First, the attacker renders this HTML document: The <img tag contains the following SVG content: As expected, the resulting PDF contains a broken image: <img width="621" height="193" alt="image" src="https://github.com/user-attachments/assets/b615fabe-c578-4435-bcb4-e9ad0ac796d2" / However, when supplying a path to a file or directory that does not exist, for example: The resulting PDF is rendered…

Published by the source

22 Jul 2026, 22:52 UTC

Last modified by the source

22 Jul 2026, 22:52 UTC

Source last checked

26 Oct 2026, 14:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j8qw-6jw8-r297

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-59943

Advisory: Dompdf: Embedded SVG images can leak existence of files and directories within the filesystem
IDs: CVE-2026-59943, GHSA-j8qw-6jw8-r297
Record: https://patchnext.com/advisories/cve-2026-59943 (revision 1, source checked 26 Oct 2026, 14:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: dompdf/dompdf 3.1.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist dompdf/dompdf: affected < 3.1.6; fixed in 3.1.6

## Suggested inspection (read-only)
- Packagist dompdf/dompdf: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dompdf/dompdf.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j8qw-6jw8-r297 (GitHub-reviewed advisory GHSA-j8qw-6jw8-r297 lists affected ranges: Packagist dompdf/dompdf >=0 <3.1.6)

Commands are suggestions: review each one before running it.