← Back
CVE-2026-49359
medium
CVSS 6.5
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**SSRF** (CWE-918) exists in pontedilana/php-weasyprint. Attackers reach the vulnerable code path via ``attachment`` without authentication.
📍 Affected scope
pontedilana/php-weasyprint — . Attack surface: `attachment` / `Pdf` / `FILTER_VALIDATE_URL` / `http`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **2.6.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pontedilana/php-weasyprint to 2.6.0ステージング環境で 2.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
pontedilana/php-weasyprint
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.0"}]}]
References
- web https://github.com/KnpLabs/snappy/security/advisories/GHSA-c5fp-p67m-gq56
- web https://github.com/pontedilana/php-weasyprint/commit/9582dcf119a405276cf55e9e10bc577a887792cb
- web https://github.com/pontedilana/php-weasyprint/releases/tag/2.6.0
- web https://github.com/pontedilana/php-weasyprint/security/advisories/GHSA-x8g9-h984-pc36
- web https://nvd.nist.gov/vuln/detail/CVE-2026-49359
- web https://github.com/advisories/GHSA-x8g9-h984-pc36