CVE-2025-68616VulnerabilityPublished 20 Jan 2026Updated 17 Sep 2026

SUSE · Security update for python-weasyprint

Affects SUSESource GCVE Database

Compare

Authoritative record:CVE-2025-68616· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade SUSE weasyprint to 68.0 soon.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score

7.5High

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

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

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

Attack Vector: Network
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: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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 19 Jan 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 30 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 68.0.

Affected software

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

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

AI-suggested

A security update has been released to fix the SSRF vulnerability in python-weasyprint. Users should apply the update provided by the SUSE Product Security Team to remediate this issue. No additional mitigation guidance is provided, and no cloud service remediation applies.

Description

A security update for python-weasyprint addresses a server-side request forgery (SSRF) vulnerability identified as CVE-2025-68616. The issue was present in the default fetcher component of python-weasyprint. This vulnerability could allow an attacker to induce the server to make unintended requests. The update fixes this SSRF vulnerability, mitigating the associated risk.

Impact

The SSRF vulnerability could allow an attacker to cause the server running python-weasyprint to make unintended requests, potentially leading to information disclosure or interaction with internal systems. No known exploits in the wild have been reported. The impact is considered high due to the nature of SSRF vulnerabilities.

Summary

The vulnerability CVE-2025-68616 in python-weasyprint involves a server-side request forgery (SSRF) flaw in the default fetcher. This flaw could be exploited to make the server perform unauthorized requests. The SUSE Product Security Team released an update to fix this issue, as documented in the security update. No CVSS score is provided, but the severity is noted as high.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Sep 2026, 02:44 UTC

Public exploits and detectionGitHub proofs of concept

Technical details

References

Community reviews

Related threats