← Back
CVE-2026-49358 low CVSS 3.0

Vulnerability in pontedilana/php-weasyprint (CVE-2026-49358)

Summary

vulnerability in pontedilana/php-weasyprint (CVE-2026-49358). Risk of unauthorized operations or information disclosure. Exploitable via ``realpath``. Mitigation: upgrade to `2.6.0` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-49358** has been found in pontedilana/php-weasyprint. Attackers can target a specific entry point like ``realpath`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: 3.0/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-49358" on the vendor's site.
CVE-2026-49358 (pontedilana/php-weasyprint) — CWE-73 / CVSS v3 3.0 Attack vector: local / no user interaction Attack surface: `realpath` / `strncmp` / `str_starts_with` 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
**A vulnerability** (CWE-73) exists in pontedilana/php-weasyprint. Attackers reach the vulnerable code path via ``realpath`` without authentication.
📍 Affected scope
pontedilana/php-weasyprint — . Attack surface: `realpath` / `strncmp` / `str_starts_with`.
🔥 Severity
Severity: Low (CVSS 3.0/10). Risk of unauthorized operations or information disclosure
🔧 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

  1. 1
    Identify exposure identify
    grep -r 'pontedilana/php-weasyprint' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pontedilana/php-weasyprint` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch
    Upgrade pontedilana/php-weasyprint to 2.6.0

    ステージング環境で 2.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-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

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →