VulnerabilityPublished 14 Sep 2026Updated 16 Sep 2026

CVE-2026-55073: Kozea WeasyPrint · Server-Side Request Forgery (SSRF)

Affects Kozea WeasyPrintSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.2 Medium : upgrade to 70.0 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

6.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 70.0

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade WeasyPrint and weasyprint to 70.0.

Affected software

Product	Affected	Fixed in
KozeaWeasyPrint	Affected <70.0	Fixed in 70.0
PyPIweasyprint`pkg:pypi/weasyprint`Other threats	Affected <70.0	Fixed in 70.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in WeasyPrint version 70.0. Users should upgrade to version 70.0 or later to remediate this issue. No other mitigation is indicated by the vendor advisory.

Description

CVE-2026-55073 is a Server-Side Request Forgery (SSRF) vulnerability in Kozea WeasyPrint versions prior to 70.0. It allows an attacker to bypass restrictive URL fetcher configurations by exploiting the xmp_metadata or stylesheets options, potentially reading local files and embedding them in generated PDFs. This issue is fixed in version 70.0.

Impact

An attacker can bypass URL fetcher restrictions and cause the server to read and embed local files into PDF documents generated by WeasyPrint. This leads to unauthorized disclosure of local files (confidentiality impact). The CVSS 3.1 score is 6.2 (medium severity), reflecting local attack vector with low complexity and no privileges required, resulting in high confidentiality impact but no integrity or availability impact.

Summary

WeasyPrint is a tool for generating PDF documents from HTML. Versions before 70.0 have an SSRF vulnerability (CWE-918) where server-side applications that use a restrictive url_fetcher can have these restrictions bypassed via attacker-controlled inputs to HTML.write_pdf(). Specifically, in weasyprint/pdf/init.py, the xmp_metadata function calls select_source() without the document's url_fetcher, allowing local files to be read and embedded in the PDF output. Similarly, in weasyprint/document.py, the stylesheets option constructs CSS() without the document url_fetcher, enabling loading of local or internal resources and propagating a permissive fetcher through nested CSS imports and url() references. Although the stylesheets channel does not disclose stylesheet comments verbatim, the vulnerability allows unauthorized local resource access. This vulnerability is resolved in WeasyPrint version 70.0.

CWE-918Server-Side Request Forgery (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Implementation · Operation
If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Operation
If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Oct 2026, 00:46 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats