← Back
CVE-2025-68616
high
CVSS 7.5
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-601) exists in weasyprint. Attackers reach the vulnerable code path via ``default_url_fetcher`` without authentication.
📍 Affected scope
weasyprint — . Attack surface: `default_url_fetcher` / `localhost` / `url_fetcher` / `urllib`.
🔥 Severity
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **68.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 '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 'weasyprint' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `weasyprint` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade weasyprint to 68.0ステージング環境で 68.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
weasyprint
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"68.0"}]}]
References
- web https://github.com/Kozea/WeasyPrint/commit/b6a14f0f3f4ce9c0c75c1a2d73cb1c5d43f0e565
- web https://github.com/Kozea/WeasyPrint/security/advisories/GHSA-983w-rhvv-gwmv
- web https://access.redhat.com/security/cve/CVE-2025-68616
- web https://bugzilla.redhat.com/show_bug.cgi?id=2430858
- web https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-68616.json
- web https://nvd.nist.gov/vuln/detail/CVE-2025-68616
- web https://github.com/advisories/GHSA-983w-rhvv-gwmv