VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pdoc: vulnerability history, versions and safety

pdoc is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 104 releases, from Jun 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 H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 pdoc vulnerabilities

Vulert verdict on pdoc 16.0.0 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 16.0.0 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 7.2 i
  • With no published fix 0 i
  • Depended on by 89 packages i
  • Stars 2,518 i
  • OpenSSF scorecard 4/10 i
  • Last release 11 months ago i
  • Licence MIT-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 pdoc, 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
16.0.0 27 Oct 2025 none MIT-0 — Details →
15.0.4 04 Jun 2025 none MIT-0 — Details →
15.0.3 21 Apr 2025 none MIT-0 — Details →
15.0.2 17 Apr 2025 none MIT-0 — Details →
15.0.1 12 Dec 2024 none MIT-0 — Details →
15.0.0 11 Oct 2024 none MIT-0 — Details →
14.7.0 11 Sep 2024 none MIT-0 — Details →
14.6.1 27 Aug 2024 none MIT-0 — Details →
14.6.0 24 Jul 2024 none MIT-0 — Details →
14.5.1 25 Jun 2024 none Unlicense — Details →
14.5.0 18 May 2024 H1 U1 Unlicense Yes Details →
14.4.0 17 Jan 2024 H1 U1 Unlicense Yes Details →
14.3.0 22 Dec 2023 H1 U1 Unlicense Yes Details →
14.2.0 13 Dec 2023 H1 U1 Unlicense Yes Details →
14.1.0 10 Sep 2023 H1 U1 Unlicense Yes Details →
14.0.0 19 Jun 2023 H1 U1 Unlicense Yes Details →
13.1.1 24 Apr 2023 H1 U1 Unlicense Yes Details →
13.1.0 31 Mar 2023 H1 U1 Unlicense Yes Details →
13.0.1 21 Mar 2023 H1 U1 Unlicense Yes Details →
13.0.0 19 Feb 2023 H1 U1 Unlicense Yes Details →
12.3.1 06 Jan 2023 H1 U1 Unlicense Yes Details →
12.3.0 15 Nov 2022 H1 U1 Unlicense Yes Details →
12.2.2 10 Nov 2022 H1 U1 Unlicense Yes Details →
12.2.1 05 Nov 2022 H1 U1 Unlicense Yes Details →
12.2.0 20 Sep 2022 H1 U1 Unlicense Yes Details →
12.1.0 11 Aug 2022 H1 U1 Unlicense Yes Details →
12.0.2 08 Jun 2022 H1 U1 Unlicense Yes Details →
12.0.1 03 Jun 2022 H1 U1 Unlicense Yes Details →
12.0.0 15 May 2022 H1 U1 Unlicense Yes Details →
11.2.0 04 May 2022 H1 U1 Unlicense Yes Details →
11.1.0 24 Apr 2022 H1 U1 Unlicense Yes Details →
11.0.0 06 Apr 2022 H1 U1 Unlicense Yes Details →
10.0.4 23 Mar 2022 H1 U1 Unlicense Yes Details →
10.0.3 08 Mar 2022 H1 U1 Unlicense Yes Details →
10.0.2 01 Mar 2022 H1 U1 Unlicense Yes Details →
10.0.1 14 Feb 2022 H1 U1 Unlicense Yes Details →
10.0.0 14 Feb 2022 H1 U1 Unlicense Yes Details →
9.0.1 26 Jan 2022 H1 U1 Unlicense Yes Details →
9.0.0 24 Jan 2022 H1 U1 Unlicense Yes Details →
8.3.0 14 Jan 2022 H1 U1 Unlicense Yes Details →
8.2.0 05 Jan 2022 H1 U1 Unlicense Yes Details →
8.1.0 28 Dec 2021 H1 U1 Unlicense Yes Details →
8.0.1 29 Oct 2021 H1 U1 Unlicense Yes Details →
8.0.0 19 Sep 2021 H1 U1 Unlicense Yes Details →
7.4.0 18 Aug 2021 H1 U1 Unlicense Yes Details →
7.3.1 09 Aug 2021 H1 U1 Unlicense Yes Details →
7.3.0 09 Aug 2021 H1 U1 Unlicense Yes Details →
7.2.0 28 Jul 2021 H1 U1 Unlicense Yes Details →
7.1.1 11 Jun 2021 H1 U1 Unlicense Yes Details →
7.1.0 02 Jun 2021 H1 U1 Unlicense Yes Details →
7.0.3 30 May 2021 H1 U1 Unlicense Yes Details →
7.0.2 27 May 2021 H1 U1 Unlicense Yes Details →
7.0.1 21 May 2021 H1 U1 Unlicense Yes Details →
7.0.0 12 May 2021 H1 U1 Unlicense Yes Details →
6.6.0 30 Apr 2021 H1 U1 Unlicense Yes Details →
6.5.0 30 Apr 2021 H1 U1 Unlicense Yes Details →
6.4.4 21 Apr 2021 H1 U1 Unlicense Yes Details →
6.4.3 11 Apr 2021 H1 U1 Unlicense Yes Details →
6.4.2 28 Mar 2021 H1 U1 Unlicense Yes Details →
6.4.1 19 Mar 2021 H1 U1 Unlicense Yes Details →
6.4.0 10 Mar 2021 H1 U1 Unlicense Yes Details →
6.3.2 25 Feb 2021 H1 U1 Unlicense Yes Details →
6.3.1 14 Feb 2021 H1 U1 Unlicense Yes Details →
6.3.0 14 Feb 2021 H1 U1 Unlicense Yes Details →
6.2.0 12 Feb 2021 H1 U1 Unlicense Yes Details →
6.1.1 12 Feb 2021 H1 U1 Unlicense Yes Details →
0.4.1 07 Feb 2021 H1 U1 Unlicense Yes Details →
6.1.0 07 Feb 2021 H1 U1 Unlicense Yes Details →
6.0.0 07 Feb 2021 H1 U1 Unlicense Yes Details →
5.0.0 05 Feb 2021 H1 U1 Unlicense Yes Details →
4.0.0 01 Feb 2021 H1 U1 Unlicense Yes Details →
3.0.1 26 Jan 2021 H1 U1 Unlicense Yes Details →
3.0.0 24 Jan 2021 H1 U1 Unlicense Yes Details →
2.0.0 21 Jan 2021 H1 U1 Unlicense Yes Details →
0.4.0 20 Jan 2021 H1 U1 Unlicense Yes Details →
1.1.0 19 Jan 2021 H1 U1 Unlicense Yes Details →
1.0.1 19 Jan 2021 H1 U1 Unlicense Yes Details →
1.0.0 19 Jan 2021 H1 U1 Unlicense Yes Details →
0.3.2 23 Mar 2016 H1 U1 Unlicense Yes Details →
0.3.1 02 Dec 2014 H1 U1 Unlicense Yes Details →
0.3.0 27 Nov 2014 H1 U1 Unlicense Yes Details →
0.2.4 22 Jul 2014 H1 U1 Unlicense Yes Details →
0.2.3 12 May 2014 H1 U1 Unlicense Yes Details →
0.2.2 10 May 2014 H1 U1 Unlicense Yes Details →
0.2.1 05 Mar 2014 H1 U1 Unlicense Yes Details →
0.2.0 21 Feb 2014 H1 U1 Unlicense Yes Details →
0.1.8 11 Sep 2013 H1 U1 Unlicense Yes Details →
0.1.7 10 Sep 2013 H1 U1 Unlicense Yes Details →
0.1.6 31 Aug 2013 H1 U1 Unlicense Yes Details →
0.1.5 22 Aug 2013 H1 U1 Unlicense Yes Details →
0.1.4 15 Aug 2013 H1 U1 Unlicense Yes Details →
0.1.3 15 Aug 2013 H1 U1 Unlicense Yes Details →
0.1.2 15 Aug 2013 H1 U1 Unlicense Yes Details →
0.1.1 15 Aug 2013 H1 U1 Unlicense Yes Details →
0.1.0 15 Aug 2013 H1 U1 Unlicense Yes Details →
0.0.19 15 Aug 2013 H1 U1 Unlicense Yes Details →
0.0.18 15 Aug 2013 H1 U1 Unlicense Yes Details →
0.0.17 14 Aug 2013 H1 U1 Unlicense Yes Details →
0.0.16 14 Aug 2013 H1 U1 Unlicense Yes Details →
0.0.15 13 Aug 2013 H1 U1 Unlicense Yes Details →
0.0.14 13 Aug 2013 H1 U1 — Yes Details →
0.0.13 13 Aug 2013 H1 U1 — Yes Details →
0.0.12 13 Aug 2013 H1 U1 — Yes Details →
0.0.11 12 Aug 2013 H1 U1 — Yes Details →
0.0.10 10 Aug 2013 H1 U1 — Yes Details →
0.0.9 10 Aug 2013 H1 U1 — Yes Details →
0.0.8 09 Aug 2013 H1 U1 — Yes Details →
0.0.7 09 Aug 2013 H1 U1 — Yes Details →
0.0.6 09 Aug 2013 H1 U1 — Yes Details →
0.0.5 09 Aug 2013 H1 U1 — Yes Details →
0.0.4 09 Aug 2013 H1 U1 — Yes Details →
0.0.3 09 Aug 2013 H1 U1 — Yes Details →
0.0.2 09 Aug 2013 H1 U1 — Yes Details →
0.0.1 09 Aug 2013 H1 U1 — Yes Details →

All 114 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 pdoc

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Vulnerability in pdoc: Embedding of Malicious CDN Link in Math Mode 7.2 high 14.5.1 25 Jun 2024
CVE-2024-38526: pdoc Vulnerability Linked to Malicious CDN via Math Mode 7.2 high 14.5.1 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 pdoc

Is pdoc safe to use?

Vulert records 2 vulnerabilities for pdoc in PyPI: 0 critical, 1 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 pdoc's Vulert package health score?

Vulert scores pdoc 75/100, which reads as in good shape. 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 pdoc affected?

No. 16.0.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 pdoc should I use?

16.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 pdoc have?

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

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

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