Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

WeasyPrint has a Server-Side Request Forgery (SSRF) Protection Bypass via HTTP Redirect

CVE-2025-68616GHSA-983w-rhvv-gwmv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (weasyprint 68.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2025-68616: 0.70% estimated exploitation activity in the next 30 days; percentile 53.29 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A Server-Side Request Forgery (SSRF) Protection Bypass exists in WeasyPrint's defaulturlfetcher. 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 urlfetcher 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. Details The default URL fetching mechanism in WeasyPrint (defaulturlfetcher in weasyprint/urls.py) is vulnerable to a Server-Side Request Forgery (SSRF) Protection Bypass. While WeasyPrint allows developers to define custom urlfetcher functions to validate or sanitize URLs before fetching (e.g., blocking internal IP addresses or specific ports), the underlying implementation uses Python's standard urllib.request.urlopen. By default, urllib automatically follows HTTP redirects (status codes 301, 302, 307,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-983w-rhvv-gwmv

  2. Revision 1 · created ·

    Published from osv record GHSA-983w-rhvv-gwmv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-68616

Advisory: WeasyPrint has a Server-Side Request Forgery (SSRF) Protection Bypass via HTTP Redirect
IDs: CVE-2025-68616, GHSA-983w-rhvv-gwmv
Record: https://patchnext.com/advisories/cve-2025-68616 (revision 2, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: weasyprint 68.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI weasyprint: affected < 68.0; fixed in 68.0

## Suggested inspection (read-only)
- `python -m pip show weasyprint`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on weasyprint.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-983w-rhvv-gwmv (OSV record GHSA-983w-rhvv-gwmv lists affected ranges: PyPI weasyprint >=0 <68.0 (fixed))
- Verified: https://github.com/advisories/GHSA-983w-rhvv-gwmv (GitHub-reviewed advisory GHSA-983w-rhvv-gwmv lists affected ranges: PyPI weasyprint >=0 <68.0)

Commands are suggestions: review each one before running it.

Loading voting…