Open Redirect in weasyprint (CVE-2025-68616)
Summary
Vulnerability in weasyprint (CVE-2025-68616). Confidential information can be exposed externally. Exploitable via default_url_fetcher. Mitigation: upgrade to 68.0 or later.
Original description
The description as published by the source.
WeasyPrint helps web developers to create PDF documents. Prior to version 68.0, a server-side request forgery (SSRF) protection bypass exists in WeasyPrint's default_url_fetcher. The vulnerability allows attackers to access internal network resources (such as localhost services or cloud metadata endpoints) even when a developer has implemented a custom url_fetcher to block such access. This occurs because the underlying urllib library follows HTTP redirects automatically without re-validating the new destination against the developer's security policy. Version 68.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-2025-68616 has been found in weasyprint.
Attackers can target a specific entry point like default_url_fetcher over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade weasyprint to 68.0 or later.
If unsure, ask your IT team or search "weasyprint CVE-2025-68616" on the vendor's site.
CVE-2025-68616 (weasyprint) — CWE-601 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: default_url_fetcher / localhost / url_fetcher / urllib
Patched: 68.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.
A vulnerability (CWE-601) exists in weasyprint. Attackers reach the vulnerable code path via default_url_fetcher without authentication.
Check the vendor advisory for the affected versions of weasyprint. Attack surface: default_url_fetcher / localhost / url_fetcher / urllib.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 68.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 '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 'weasyprint' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
weasyprintを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade weasyprint to 68.0ステージング環境で 68.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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-2025-68616 weasyprint
- Ubuntu UBUNTU-CVE-2025-68616 weasyprint
References
- advisory github.com
- advisory access.redhat.com
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- report bugzilla.redhat.com
- web security.access.redhat.com