PyPI PACKAGE

weasyprint 68.1

Warn

PkgFire would install this release with a warning.·Checked 11 hours ago·Published 6 February 2026

pypi.org

Why

  • warnVulnerability

    WeasyPrint has CSS Injection via Presentational Hints

  • warnVulnerability

    weasyprint Has Server-Side Request Forgery (SSRF) (fixed in 70.0)

  • warnVulnerability

    WeasyPrint: EPS images reach the Ghostscript interpreter resulting in RCE (fixed in 70.0)

  • warnVulnerability

    weasyprint Has Server-Side Request Forgery (SSRF) (fixed in 70.0)

  • warnVulnerability

    WeasyPrint has CSS Injection via Presentational Hints

  • warnVulnerability

    WeasyPrint: EPS images reach the Ghostscript interpreter resulting in RCE (fixed in 70.0)

Provenance

A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.

Signature
Not signed
Build provenance
Attested

What the code does

On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.

Code reading

PkgFire's own reading of the files: what the code can do.

  • code-networkweasyprint/__init__.py, weasyprint/pdf/anchors.py, weasyprint/svg/css.py, weasyprint/svg/utils.py, weasyprint/urls.py
  • import-networkweasyprint/__init__.py

Source patterns

Patterns found in the source, including those malware is known to use.

  • capability-filesystem-delete
  • capability-filesystem-read
  • capability-network-download
  • capability-network-outbound
  • capability-process-spawn

Other checked releases

Check every dependency before it installs

This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.

Start free How it works