VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

docutils: vulnerability history, versions and safety

docutils is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 1 release, from Oct 2019 to Mar 2020. 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 C1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all docutils vulnerabilities

Vulert verdict on docutils 0.23.0 i

Updated on 23 Oct 2026

Good news: 0.23.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 87/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

What to do: Stay on 0.23.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.23.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.23.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 13 Mar 2020 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Depended on by 9,498 packages i
  • Last release 4 months 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 docutils, 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.23.0 27 May 2026 none non-standard — Details →
0.23.0rc1 09 May 2026 none non-standard — Details →
0.22.4 18 Dec 2025 none non-standard — Details →
0.22.3 06 Nov 2025 none non-standard — Details →
0.22.2 20 Sep 2025 none non-standard — Details →
0.22.1 17 Sep 2025 none non-standard — Details →
0.22.1rc1 13 Sep 2025 none non-standard — Details →
0.22.0 29 Jul 2025 none non-standard — Details →
0.22.0rc5 24 Jun 2025 none non-standard — Details →
0.22.0rc4 17 Jun 2025 none non-standard — Details →
0.22.0rc3 10 Jun 2025 none non-standard — Details →
0.22.0rc2 22 May 2025 none non-standard — Details →
0.22.0rc1 06 May 2025 none non-standard — Details →
0.21.2 23 Apr 2024 none non-standard — Details →
0.21.1 10 Apr 2024 none non-standard — Details →
0.21.0 09 Apr 2024 none non-standard — Details →
0.21.0rc1 26 Mar 2024 none non-standard — Details →
0.20.1 16 May 2023 none non-standard — Details →
0.20.0 09 May 2023 none non-standard — Details →
0.20.0rc1 04 May 2023 none non-standard — Details →
0.19.0 05 Jul 2022 none non-standard — Details →
0.19.0b1 21 Jun 2022 none non-standard — Details →
0.18.1 23 Nov 2021 none non-standard — Details →
0.18.1b0 18 Nov 2021 none non-standard — Details →
0.18.0 26 Oct 2021 none non-standard — Details →
0.18.0b1 05 Oct 2021 none non-standard — Details →
0.17.1 17 Apr 2021 none non-standard — Details →
0.17.1b1.dev0 09 Apr 2021 none non-standard — Details →
0.17.0 03 Apr 2021 none non-standard — Details →
0.17.0b1 10 Feb 2021 none non-standard — Details →
0.16.0 12 Jan 2020 none non-standard — Details →
0.16.0rc1 19 Dec 2019 none non-standard — Details →
0.16.0b0.dev0 04 Dec 2019 none non-standard — Details →
0.15.2 30 Jul 2019 none non-standard — Details →
0.15.0 21 Jul 2019 none non-standard — Details →
0.14.0 03 Aug 2017 none non-standard — Details →
0.14.0rc2 08 Jul 2017 none non-standard — Details →
0.14.0rc1 27 May 2017 none non-standard — Details →
0.13.1 09 Dec 2016 none non-standard — Details →
0.12.0 07 May 2015 none non-standard — Details →
0.4.0 24 Jul 2013 none non-standard — Details →
0.3.9 24 Jul 2013 none non-standard — Details →
0.3.7 24 Jul 2013 none non-standard — Details →
0.3.5 24 Jul 2013 none non-standard — Details →
0.3.0 24 Jul 2013 none non-standard — Details →
0.5.0 23 Jul 2013 C1 U1 non-standard Yes Details →
0.11.0 23 Jul 2013 none non-standard — Details →
0.10.0 16 Dec 2012 none non-standard — Details →
0.9.0 30 Aug 2012 none non-standard — Details →
0.9.1 16 Aug 2012 none non-standard — Details →
0.8.1 18 Oct 2011 none non-standard — Details →
0.8.0 08 Jul 2011 none non-standard — Details →
0.7.0 07 Jul 2010 none non-standard — Details →
0.6.0 28 Dec 2009 none non-standard — Details →
0.15.0.post1 — none — — Details →
0.15.1 — none — — Details →
0.15.1.post1 — none non-standard — Details →
0.21.0.post1 — none non-standard — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for docutils

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2009-5042: Insecure Usage of Temporary Files in python-docutils 9.1 critical 0.6 13 Mar 2020
CVE-2009-5042: Insecure Usage of Temporary Files in python-docutils N/A unrated 0.6 31 Oct 2019

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 docutils

Is docutils safe to use?

Vulert records 2 vulnerabilities for docutils in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is docutils's Vulert package health score?

Vulert scores docutils 87/100, which reads as healthy. 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).

Is the latest version of docutils affected?

No. 0.23.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of docutils should I use?

0.23.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 docutils have?

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

0 vulnerabilities were recorded for docutils in the last 12 months, and the oldest entry in this database dates to 31 Oct 2019. 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 docutils 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 docutils for upcoming vulnerabilities?

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