SSRF (Server-Side Request Forgery) in pontedilana/php-weasyprint (CVE-2026-49359)
Summary
SSRF in pontedilana/php-weasyprint (CVE-2026-49359). Confidential information can be exposed externally. Exploitable via attachment. Mitigation: upgrade to 2.6.0 or later.
Original description
The description as published by the source.
PhpWeasyPrint is a PHP library allowing PDF generation from a URL or an HTML page. Prior to version 2.6.0, pontedilana/php-weasyprint fetches the content of option values server-side via file_get_contents() when the value looks like a URL, without restricting the URL scheme. The attachment option of Pdf is the reachable sink: any value that passes isOptionUrl() (filter_var(..., FILTER_VALIDATE_URL)) is downloaded by the PHP process and embedded into the generated PDF. Because FILTER_VALIDATE_URL accepts http, https, ftp, file and PHP stream wrappers such as php://, an attacker who can influence the attachment value reaches both a Server-Side Request Forgery primitive (e.g. internal HTTP endpoints, cloud metadata) and a local file disclosure primitive (file://, php://filter/...), with the fetched bytes exfiltrated as a PDF attachment. This is the same class of issue KnpLabs/snappy patched for its xsl-style-sheet option in GHSA-c5fp-p67m-gq56. The library is documented as a one-to-one substitute for KnpLabs/snappy and shares the same code shape. PhpWeasyPrint version 2.6.0 contains a patch for the issue.
Source: NIST National Vulnerability Database 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-49359 has been found in pontedilana/php-weasyprint.
Attackers can target a specific entry point like attachment over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade pontedilana/php-weasyprint to 2.6.0 or later.
If unsure, ask your IT team or search "pontedilana/php-weasyprint CVE-2026-49359" on the vendor's site.
CVE-2026-49359 (pontedilana/php-weasyprint) — CWE-918 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: attachment / Pdf / FILTER_VALIDATE_URL / http
Patched: 2.6.0 — 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.
SSRF (CWE-918) exists in pontedilana/php-weasyprint. Attackers reach the vulnerable code path via attachment.
Check the vendor advisory for the affected versions of pontedilana/php-weasyprint. Attack surface: attachment / Pdf / FILTER_VALIDATE_URL / http.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 2.6.0.
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 'pontedilana/php-weasyprint' . 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 'pontedilana/php-weasyprint' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pontedilana/php-weasyprintを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pontedilana/php-weasyprint to 2.6.0ステージング環境で 2.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web github.com
- web github.com