Vulnerability in dompdf/dompdf (CVE-2026-59943)
Summary
Vulnerability in dompdf/dompdf (CVE-2026-59943). Risk of unauthorized operations or information disclosure. Exploitable via href. Mitigation: upgrade to 3.1.6 or later.
Original description
The description as published by the source.
Dompdf is an HTML to PDF converter for PHP. In versions 3.15 and prior, 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. Using an 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. This issue has been fixed in version 3.16.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-59943 has been found in dompdf/dompdf.
Attackers can target a specific entry point like href over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade dompdf/dompdf to 3.1.6 or later.
If unsure, ask your IT team or search "dompdf/dompdf CVE-2026-59943" on the vendor's site.
CVE-2026-59943 (dompdf/dompdf) — CWE-209 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: href
Patched: 3.1.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-209) exists in dompdf/dompdf. Attackers reach the vulnerable code path via href without authentication.
Check the vendor advisory for the affected versions of dompdf/dompdf. Attack surface: href.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 3.1.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'dompdf/dompdf' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'dompdf/dompdf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
dompdf/dompdfを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade dompdf/dompdf to 3.1.6ステージング環境で 3.1.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-59943 php-dompdf
- Ubuntu UBUNTU-CVE-2026-59943 php-dompdf
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com