VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

weasyprint: vulnerability history, versions and safety

weasyprint is a package in the PyPI ecosystem. Vulert records 10 vulnerabilities for it across 120 releases, from Mar 2024 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded H3 M2 U5
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
9 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all weasyprint vulnerabilities

Vulert verdict on weasyprint 70.0.0 i

Updated on 23 Oct 2026

Careful: 70.0.0 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 70.0.0 — affected i
  • Vulnerabilities on record 10 over 2 years · 9 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 2 i
  • Depended on by 550 packages i
  • Stars 9,718 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for weasyprint, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
70.0.0 08 Sep 2026 M1 U1 non-standard No Details →
69.0.0 02 Jun 2026 H1 M2 U3 non-standard No Details →
68.1.0 06 Feb 2026 H1 M2 U3 non-standard No Details →
68.0.0 19 Jan 2026 H1 M2 U3 non-standard No Details →
67.0.0 02 Dec 2025 H2 M2 U4 non-standard No Details →
66.0.0 24 Jul 2025 H2 M2 U4 non-standard No Details →
65.1.0 14 Apr 2025 H2 M2 U4 non-standard No Details →
65.0.0 20 Mar 2025 H2 M2 U4 non-standard No Details →
64.1.0 20 Feb 2025 H2 M2 U4 non-standard No Details →
64.0.0 30 Jan 2025 H2 M2 U4 non-standard No Details →
63.1.0 10 Dec 2024 H2 M2 U4 non-standard No Details →
63.0.0 29 Oct 2024 H2 M2 U4 non-standard No Details →
62.3.0 21 Jun 2024 H2 M2 U4 non-standard No Details →
62.2.0 04 Jun 2024 H2 M2 U4 non-standard No Details →
62.1.0 06 May 2024 H2 M2 U4 non-standard No Details →
62.0.0 30 Apr 2024 H2 M2 U4 non-standard No Details →
61.2.0 08 Mar 2024 H2 M2 U4 non-standard No Details →
61.1.0 26 Feb 2024 H3 M2 U5 non-standard No Details →
61.0.0 12 Feb 2024 H3 M2 U5 non-standard No Details →
60.2.0 11 Dec 2023 H2 M2 U4 non-standard No Details →
60.1.0 29 Sep 2023 H2 M2 U4 non-standard No Details →
60.0.0 25 Sep 2023 H2 M2 U4 non-standard No Details →
59.0.0 11 May 2023 H2 M2 U4 non-standard No Details →
59.0.0b1 14 Apr 2023 H2 M2 U4 non-standard No Details →
58.1.0 07 Mar 2023 H2 M2 U4 non-standard No Details →
58.0.0 17 Feb 2023 H2 M2 U4 non-standard No Details →
58.0.0b1 03 Feb 2023 H2 M2 U4 non-standard No Details →
57.2.0 23 Dec 2022 H2 M2 U4 non-standard No Details →
57.1.0 04 Nov 2022 H2 M2 U4 non-standard No Details →
57.0.0 18 Oct 2022 H2 M2 U4 non-standard No Details →
57.0.0b1 22 Sep 2022 H2 M2 U4 non-standard No Details →
56.1.0 24 Jul 2022 H2 M2 U4 non-standard No Details →
56.0.0 07 Jul 2022 H2 M2 U4 non-standard No Details →
56.0.0b1 17 Jun 2022 H2 M2 U4 non-standard No Details →
55.0.0 12 May 2022 H2 M2 U4 non-standard No Details →
55.0.0b1 15 Apr 2022 H2 M2 U4 non-standard No Details →
54.3.0 04 Apr 2022 H2 M2 U4 non-standard No Details →
54.2.0 27 Feb 2022 H2 M2 U4 non-standard No Details →
54.1.0 31 Jan 2022 H2 M2 U4 non-standard No Details →
54.0.0 08 Jan 2022 H2 M2 U4 non-standard No Details →
54.0.0b1 13 Dec 2021 H2 M2 U4 non-standard No Details →
53.4.0 14 Nov 2021 H2 M2 U4 non-standard No Details →
53.3.0 10 Sep 2021 H2 M2 U4 non-standard No Details →
53.2.0 27 Aug 2021 H2 M2 U4 non-standard No Details →
53.1.0 22 Aug 2021 H2 M2 U4 non-standard No Details →
53.0.0 31 Jul 2021 H2 M2 U4 non-standard No Details →
53.0.0b2 30 May 2021 H2 M2 U4 non-standard No Details →
53.0.0b1 22 Apr 2021 H2 M2 U4 non-standard No Details →
52.5.0 17 Apr 2021 H2 M2 U4 non-standard No Details →
52.4.0 11 Mar 2021 H2 M2 U4 non-standard No Details →
52.3.0 02 Mar 2021 H2 M2 U4 non-standard No Details →
52.2.0 06 Dec 2020 H2 M2 U4 non-standard No Details →
52.1.0 02 Nov 2020 H2 M2 U4 non-standard No Details →
52.0.0 29 Oct 2020 H2 M2 U4 non-standard No Details →
51.0.0 23 Dec 2019 H2 M2 U4 non-standard No Details →
50.0.0 19 Sep 2019 H2 M2 U4 non-standard No Details →
49.0.0 11 Sep 2019 H2 M2 U4 non-standard No Details →
48.0.0 08 Jul 2019 H2 M2 U4 non-standard No Details →
47.0.0 12 Apr 2019 H2 M2 U4 non-standard No Details →
46.0.0 20 Mar 2019 H2 M2 U4 non-standard No Details →
45.0.0 20 Feb 2019 H2 M2 U4 non-standard No Details →
44.0.0 29 Dec 2018 H2 M2 U4 BSD-3-Clause No Details →
43.0.0 09 Nov 2018 H2 M2 U4 BSD-3-Clause No Details →
43.0.0rc2 02 Nov 2018 H2 M2 U4 BSD-3-Clause No Details →
43.0.0rc1 15 Oct 2018 H2 M2 U4 BSD-3-Clause No Details →
0.42.3 27 Mar 2018 H2 M2 U4 non-standard No Details →
0.42.2 04 Feb 2018 H2 M2 U4 non-standard No Details →
0.42.1 01 Feb 2018 H2 M2 U4 non-standard No Details →
0.42.0 26 Dec 2017 H2 M2 U4 non-standard No Details →
0.41.0 05 Oct 2017 H2 M2 U4 non-standard No Details →
0.40.0 17 Aug 2017 H2 M2 U4 non-standard No Details →
0.39.0 24 Jun 2017 H2 M2 U4 non-standard No Details →
0.38.0 16 Jun 2017 H2 M2 U4 non-standard No Details →
0.37.0 15 Jun 2017 H2 M2 U4 non-standard No Details →
0.36.0 25 Feb 2017 H2 M2 U4 non-standard No Details →
0.35.0 25 Feb 2017 H2 M2 U4 non-standard No Details →
0.34.0 21 Dec 2016 H2 M2 U4 non-standard No Details →
0.33.0 28 Nov 2016 H2 M2 U4 non-standard No Details →
0.32.0 17 Nov 2016 H2 M2 U4 non-standard No Details →
0.31.0 28 Aug 2016 H2 M2 U4 non-standard No Details →
0.30.0 19 Jul 2016 H2 M2 U4 non-standard No Details →
0.29.0 17 Jun 2016 H2 M2 U4 non-standard No Details →
0.28.0 16 May 2016 H2 M2 U4 non-standard No Details →
0.27.0 08 Apr 2016 H2 M2 U4 non-standard No Details →
0.26.0 29 Jan 2016 H2 M2 U4 non-standard No Details →
0.25.0 17 Dec 2015 H2 M2 U4 non-standard No Details →
0.24.0 04 Aug 2015 H2 M2 U4 non-standard No Details →
0.23.0 16 Sep 2014 H2 M2 U4 non-standard No Details →
0.22.0 05 May 2014 H2 M2 U4 non-standard No Details →
0.21.0 11 Jan 2014 H2 M2 U4 non-standard No Details →
0.20.2 18 Dec 2013 H2 M2 U4 non-standard No Details →
0.20.1 16 Dec 2013 H2 M2 U4 non-standard No Details →
0.20.0 14 Dec 2013 H2 M2 U4 non-standard No Details →
0.19.2 18 Jun 2013 H2 M2 U4 non-standard No Details →
0.19.1 30 Apr 2013 H2 M2 U4 non-standard No Details →
0.19.0 18 Apr 2013 H2 M2 U4 non-standard No Details →
0.18.0 30 Mar 2013 H2 M2 U4 non-standard No Details →
0.17.1 18 Mar 2013 H2 M2 U4 non-standard No Details →
0.17.0 27 Feb 2013 H2 M2 U4 non-standard No Details →
0.16.0 13 Dec 2012 H2 M2 U4 non-standard No Details →
0.15.0 09 Oct 2012 H2 M2 U4 — No Details →
0.14.0 03 Aug 2012 H2 M2 U4 — No Details →
0.13.0 23 Jul 2012 H2 M2 U4 — No Details →
0.12.0 19 Jul 2012 H2 M2 U4 — No Details →
0.11.0 04 Jul 2012 H2 M2 U4 — No Details →
0.10.0 25 Jun 2012 H2 M2 U4 — No Details →
0.9.0 04 Jun 2012 H2 M2 U4 — No Details →
0.8.0 07 May 2012 H2 M2 U4 — No Details →
0.7.1 21 Mar 2012 H2 M2 U4 — No Details →
0.7.0 21 Mar 2012 H2 M2 U4 — No Details →
0.6.1 01 Mar 2012 H2 M2 U4 — No Details →
0.6.0 29 Feb 2012 H2 M2 U4 — No Details →
0.5.0 08 Feb 2012 H2 M2 U4 — No Details →
0.4.0 07 Feb 2012 H2 M2 U4 — No Details →
0.3.1 14 Dec 2011 H2 M2 U4 — No Details →
0.3.0 13 Dec 2011 H2 M2 U4 — No Details →
0.2.2 29 Nov 2011 H2 M2 U4 — No Details →
0.2.1 25 Nov 2011 H2 M2 U4 — No Details →
0.2.0 25 Nov 2011 H2 M2 U4 — No Details →
0.1.0 28 Oct 2011 H2 M2 U4 — No Details →

All 120 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 9

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 9 of the 10 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for weasyprint

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-106443: WeasyPrint Remote Code Execution via EPS Image Processing 8.8 high 70.0 07 Oct 2026
CVE-2026-106443: WeasyPrint Remote Code Execution via Untrusted EPS Images 8.8 high 70.0 15 Oct 2026
CVE-2025-68616: WeasyPrint SSRF Protection Bypass via HTTP Redirect 7.5 high 68.0 20 Jan 2026
CVE-2025-68616 WeasyPrint SSRF Protection Bypass Vulnerability 7.5 high 68.0 07 Jul 2026
CVE-2024-28184: Arbitrary File Attachment in WeasyPrint PDF Generation 7.4 high 61.2 08 Mar 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About weasyprint

Is weasyprint safe to use?

Vulert records 10 vulnerabilities for weasyprint in PyPI: 0 critical, 3 high, 2 medium and 0 low, plus 5 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is weasyprint's Vulert package health score?

Vulert scores weasyprint 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of weasyprint affected?

Yes. 70.0.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of weasyprint should I use?

70.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does weasyprint have?

10 vulnerabilities are recorded for weasyprint in the PyPI ecosystem: 0 critical, 3 high, 2 medium and 0 low, plus 5 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new weasyprint vulnerabilities disclosed?

9 vulnerabilities were recorded for weasyprint in the last 12 months, and the oldest entry in this database dates to 08 Mar 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of weasyprint are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor weasyprint for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the weasyprint version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.