VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

xhtml2pdf: vulnerability history, versions and safety

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

i
2 vulnerabilities recorded M1 U1
i
2 with no fix published

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

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

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all xhtml2pdf vulnerabilities

Vulert verdict on xhtml2pdf 0.2.27 i

Updated on 23 Oct 2026

Careful: 0.2.27 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 Some issues to review
  • 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 0.2.27 — affected i
  • Vulnerabilities on record 2 over 1 year · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 5.3 i
  • With no published fix 2 i
  • Depended on by 96 packages i
  • Stars 2,396 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence Apache-2.0 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 xhtml2pdf, 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
0.2.27 21 Oct 2026 M1 U1 Apache-2.0 No Details →
0.2.26 16 Oct 2026 M1 U1 Apache-2.0 No Details →
0.2.25 16 Oct 2026 M1 U1 non-standard No Details →
0.2.24 15 Oct 2026 M1 U1 non-standard No Details →
0.2.23 08 Oct 2026 M1 U1 non-standard No Details →
0.2.22 07 Oct 2026 M1 U1 non-standard No Details →
0.2.21 26 Sep 2026 M1 U1 non-standard No Details →
0.2.20 16 Sep 2026 M1 U1 non-standard No Details →
0.2.19 12 Sep 2026 M1 U1 non-standard No Details →
0.2.18 03 Sep 2026 M1 U1 non-standard No Details →
0.2.17 24 Feb 2025 M1 U1 non-standard No Details →
0.2.16 08 Jun 2024 M1 U1 non-standard No Details →
0.2.15 08 Feb 2024 M1 U1 non-standard No Details →
0.2.14 20 Jan 2024 M1 U1 non-standard No Details →
0.2.13 09 Nov 2023 M1 U1 non-standard No Details →
0.2.12 08 Nov 2023 M1 U1 non-standard No Details →
0.2.11 07 May 2023 M1 U1 Apache-2.0 No Details →
0.2.10 19 Apr 2023 M1 U1 Apache-2.0 No Details →
0.2.9 30 Jan 2023 M1 U1 Apache-2.0 No Details →
0.2.8 16 Jun 2022 M1 U1 Apache-2.0 No Details →
0.2.7 31 Mar 2022 M1 U1 Apache-2.0 No Details →
0.2.6 11 Mar 2022 M1 U1 Apache-2.0 No Details →
0.2.5 08 Oct 2020 M1 U1 Apache-2.0 No Details →
0.2.4 18 Jan 2020 M1 U1 Apache-2.0 No Details →
0.2.3 14 Sep 2018 M1 U1 Apache-2.0 No Details →
0.2.2 16 Apr 2018 M1 U1 Apache-2.0 No Details →
0.2.1 15 Feb 2018 M1 U1 Apache-2.0 No Details →
0.2.0 15 Feb 2018 M1 U1 Apache-2.0 No Details →
0.2.0b1 30 Nov 2016 M1 U1 Apache-2.0 No Details →
0.1.0b3 16 Aug 2016 M1 U1 Apache-2.0 No Details →
0.1.0b2 01 Aug 2016 M1 U1 Apache-2.0 No Details →
0.1.0b1 04 Jun 2016 M1 U1 Apache-2.0 No Details →
0.1.0a4 18 May 2016 M1 U1 Apache-2.0 No Details →
0.1.0a3 01 May 2016 M1 U1 Apache-2.0 No Details →
0.1.0a2 14 Apr 2016 M1 U1 Apache-2.0 No Details →
0.1.0a1 20 Jan 2016 M1 U1 Apache-2.0 No Details →
0.0.6 27 Apr 2014 M1 U1 Apache-2.0 No Details →
0.0.5 25 Mar 2013 M1 U1 Apache-2.0 No Details →
0.0.4 23 May 2012 M1 U1 Apache-2.0 No Details →
0.0.3 19 Jul 2011 M1 U1 Apache-2.0 No Details →
0.0.2 27 May 2011 M1 U1 Apache-2.0 No Details →
0.0.1 20 May 2011 M1 U1 Apache-2.0 No Details →

All 42 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 1

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

03 Vulnerabilities

Recorded vulnerabilities for xhtml2pdf

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-25885: xhtml2pdf Denial of Service via Crafted String 5.3 medium No fix published 08 Oct 2024
CVE-2024-25885: xhtml2pdf Denial of Service via Crafted String 5.3 medium No fix published 07 Jul 2026

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 xhtml2pdf

Is xhtml2pdf safe to use?

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

What is xhtml2pdf's Vulert package health score?

Vulert scores xhtml2pdf 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 xhtml2pdf affected?

Yes. 0.2.27, 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.

How many vulnerabilities does xhtml2pdf have?

2 vulnerabilities are recorded for xhtml2pdf in the PyPI ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 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 xhtml2pdf vulnerabilities disclosed?

1 vulnerability was recorded for xhtml2pdf in the last 12 months, and the oldest entry in this database dates to 08 Oct 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 xhtml2pdf 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 xhtml2pdf for upcoming vulnerabilities?

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