CVE-2025-68616
Kozea Weasyprint server-side request forgery (SSRF)
- Published19 Jan 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NAffected products
Remediation
References
- https://access.redhat.com/security/cve/CVE-2025-68616
- https://bugzilla.redhat.com/show_bug.cgi?id=2430858
- https://github.com/Kozea/WeasyPrint/commit/b6a14f0f3f4ce9c0c75c1a2d73cb1c5d43f0e565
- https://github.com/Kozea/WeasyPrint/security/advisories/GHSA-983w-rhvv-gwmv
- https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-68616.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-68616 being actively exploited?
CVE-2025-68616 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.71%.
How severe is CVE-2025-68616?
CVE-2025-68616 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.71% probability of exploitation.
Which products are affected by CVE-2025-68616?
Affected products include Kozea Weasyprint.
How do I fix CVE-2025-68616?
Upgrade affected software to a fixed version, for example Kozea Weasyprint 68.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-68616 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.