VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pydantic: vulnerability history, versions and safety

pydantic is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 120 releases, from May 2021 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
4 vulnerabilities recorded M2 U2
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 pydantic vulnerabilities

Vulert verdict on pydantic 2.14.1 i

Updated on 23 Oct 2026

Action needed: 2.14.1 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 90/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 2.14.1 — affected i
  • Vulnerabilities on record 4 over 5 years · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 5.9 i
  • With no published fix 0 i
  • Depended on by 132,302 packages i
  • Stars 29,123 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence MIT 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 pydantic, 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
2.14.1 11 Oct 2026 U1 MIT Yes Details →
2.14.0 08 Oct 2026 U1 MIT Yes Details →
2.14.0b2 09 Sep 2026 U1 MIT Yes Details →
2.13.5 28 Aug 2026 U1 MIT Yes Details →
2.14.0b1 06 Aug 2026 U1 MIT Yes Details →
2.14.0a1 22 May 2026 U1 MIT Yes Details →
2.13.4 06 May 2026 U1 MIT Yes Details →
2.13.3 20 Apr 2026 U1 MIT Yes Details →
2.13.2 17 Apr 2026 U1 MIT Yes Details →
2.13.1 15 Apr 2026 U1 MIT Yes Details →
2.13.0 13 Apr 2026 U1 MIT Yes Details →
2.13.0b3 31 Mar 2026 U1 MIT Yes Details →
2.13.0b2 24 Feb 2026 U1 MIT Yes Details →
2.13.0b1 23 Feb 2026 U1 MIT Yes Details →
1.10.26 18 Dec 2025 U1 MIT Yes Details →
1.10.25 18 Dec 2025 U1 MIT Yes Details →
2.12.5 26 Nov 2025 U1 MIT Yes Details →
2.12.4 05 Nov 2025 U1 MIT Yes Details →
2.12.3 17 Oct 2025 U1 MIT Yes Details →
2.12.2 14 Oct 2025 U1 MIT Yes Details →
2.12.1 13 Oct 2025 U1 MIT Yes Details →
2.12.0 07 Oct 2025 U1 MIT Yes Details →
2.11.10 04 Oct 2025 U1 MIT Yes Details →
2.12.0b1 02 Oct 2025 U1 MIT Yes Details →
1.10.24 25 Sep 2025 U1 MIT Yes Details →
2.11.9 13 Sep 2025 U1 MIT Yes Details →
1.10.23 13 Sep 2025 U1 MIT Yes Details →
2.11.8 13 Sep 2025 U1 MIT Yes Details →
2.12.0a1 26 Jul 2025 U1 MIT Yes Details →
2.11.7 14 Jun 2025 U1 MIT Yes Details →
2.11.6 13 Jun 2025 U1 MIT Yes Details →
2.11.5 22 May 2025 U1 MIT Yes Details →
2.11.4 29 Apr 2025 U1 MIT Yes Details →
1.10.22 24 Apr 2025 U1 MIT Yes Details →
2.11.3 08 Apr 2025 U1 MIT Yes Details →
2.11.2 03 Apr 2025 U1 MIT Yes Details →
2.11.1 28 Mar 2025 U1 MIT Yes Details →
2.11.0 27 Mar 2025 U1 MIT Yes Details →
2.11.0b2 17 Mar 2025 U1 MIT Yes Details →
2.11.0b1 06 Mar 2025 U1 MIT Yes Details →
2.11.0a2 10 Feb 2025 U1 MIT Yes Details →
2.11.0a1 30 Jan 2025 U1 MIT Yes Details →
2.10.6 24 Jan 2025 U1 MIT Yes Details →
1.10.21 14 Jan 2025 U1 MIT Yes Details →
2.10.5 09 Jan 2025 U1 MIT Yes Details →
1.10.20 07 Jan 2025 U1 MIT Yes Details →
2.10.4 18 Dec 2024 U1 MIT Yes Details →
2.10.3 03 Dec 2024 U1 MIT Yes Details →
2.10.2 26 Nov 2024 U1 MIT Yes Details →
2.10.1 22 Nov 2024 U1 MIT Yes Details →
2.10.0 20 Nov 2024 U1 MIT Yes Details →
2.10.0b2 13 Nov 2024 U1 MIT Yes Details →
2.10.0b1 06 Nov 2024 U1 MIT Yes Details →
1.10.19 06 Nov 2024 U1 MIT Yes Details →
2.9.2 17 Sep 2024 U1 MIT Yes Details →
2.9.1 09 Sep 2024 U1 MIT Yes Details →
2.9.0 05 Sep 2024 U1 MIT Yes Details →
2.9.0b2 31 Aug 2024 U1 MIT Yes Details →
2.9.0b1 26 Aug 2024 U1 MIT Yes Details →
1.10.18 22 Aug 2024 U1 MIT Yes Details →
2.8.2 04 Jul 2024 U1 MIT Yes Details →
2.8.1 03 Jul 2024 U1 MIT Yes Details →
2.8.0 01 Jul 2024 U1 MIT Yes Details →
2.8.0b1 27 Jun 2024 U1 MIT Yes Details →
1.10.17 20 Jun 2024 U1 MIT Yes Details →
2.7.4 12 Jun 2024 U1 MIT Yes Details →
1.10.16 11 Jun 2024 U1 MIT Yes Details →
2.7.3 03 Jun 2024 U1 MIT Yes Details →
2.7.2 28 May 2024 U1 MIT Yes Details →
2.7.1 23 Apr 2024 U1 MIT Yes Details →
2.7.0 11 Apr 2024 U1 MIT Yes Details →
2.7.0b1 03 Apr 2024 U1 MIT Yes Details →
1.10.15 03 Apr 2024 U1 MIT Yes Details →
2.6.4 12 Mar 2024 U1 MIT Yes Details →
2.6.3 27 Feb 2024 U1 MIT Yes Details →
2.6.2 23 Feb 2024 U1 MIT Yes Details →
2.6.1 05 Feb 2024 U1 MIT Yes Details →
2.6.0 29 Jan 2024 U1 MIT Yes Details →
2.6.0b1 19 Jan 2024 U1 MIT Yes Details →
1.10.14 19 Jan 2024 U1 MIT Yes Details →
2.5.3 22 Dec 2023 U1 MIT Yes Details →
2.5.2 22 Nov 2023 U1 MIT Yes Details →
2.5.1 15 Nov 2023 U1 MIT Yes Details →
2.5.0 13 Nov 2023 U1 MIT Yes Details →
2.5.0b1 09 Nov 2023 U1 MIT Yes Details →
2.4.2 28 Sep 2023 U1 MIT Yes Details →
1.10.13 27 Sep 2023 U1 MIT Yes Details →
2.4.1 26 Sep 2023 U1 MIT Yes Details →
2.4.0 25 Sep 2023 U1 MIT Yes Details →
2.3.0 23 Aug 2023 M1 U1 MIT Yes Details →
2.2.1 18 Aug 2023 M1 U1 MIT Yes Details →
2.2.0 17 Aug 2023 M1 U1 MIT Yes Details →
2.1.1 25 Jul 2023 M1 U1 MIT Yes Details →
2.1.0 25 Jul 2023 M1 U1 MIT Yes Details →
1.10.12 24 Jul 2023 U1 MIT Yes Details →
2.0.3 14 Jul 2023 M1 U1 MIT Yes Details →
2.0.2 05 Jul 2023 M1 U1 MIT Yes Details →
2.0.1 04 Jul 2023 M1 U1 MIT Yes Details →
1.10.11 04 Jul 2023 U1 MIT Yes Details →
2.0.0 30 Jun 2023 M1 U1 MIT Yes Details →
1.10.10 30 Jun 2023 U1 — Yes Details →
2.0.0b3 17 Jun 2023 U1 — Yes Details →
1.10.9 07 Jun 2023 U1 — Yes Details →
2.0.0b2 03 Jun 2023 U1 — Yes Details →
2.0.0b1 01 Jun 2023 U1 — Yes Details →
1.10.8 23 May 2023 U1 — Yes Details →
2.0.0a4 05 May 2023 U1 — Yes Details →
2.0.0a3 20 Apr 2023 U1 — Yes Details →
2.0.0a2 12 Apr 2023 U1 — Yes Details →
2.0.0a1 03 Apr 2023 U1 — Yes Details →
1.10.7 22 Mar 2023 U1 — Yes Details →
1.10.6 08 Mar 2023 U1 — Yes Details →
1.10.5 15 Feb 2023 U1 — Yes Details →
1.10.4 30 Dec 2022 U1 — Yes Details →
1.10.3 29 Dec 2022 U1 — Yes Details →
1.10.2 05 Sep 2022 U1 — Yes Details →
1.10.1 31 Aug 2022 U1 — Yes Details →
1.10.0 30 Aug 2022 U1 — Yes Details →
1.10.0b1 24 Aug 2022 U1 — Yes Details →
1.10.0a2 24 Aug 2022 U1 — Yes Details →

The newest 120 of 208 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2024 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for pydantic

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Pydantic Regular Expression Denial of Service 5.9 medium 2.4.0 15 Apr 2024
CVE-2024-3772: Pydantic Regular Expression Denial of Service Vulnerability 5.9 medium 1.10.13 07 Jul 2026
CVE-2021-29510: pydantic - Use of "infinity" as an input to datetime and date fields causes infinite loop 3.3 medium 1.6.2 13 May 2021
CVE-2021-29510: Pydantic - Denial of Service (DoS) via Infinite Loop N/A unrated 7e83fdd2563ffac081db7ecdf1affa65ef38c468 13 May 2021

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 pydantic

Is pydantic safe to use?

Vulert records 4 vulnerabilities for pydantic in PyPI: 0 critical, 0 high, 2 medium and 0 low, plus 2 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 pydantic's Vulert package health score?

Vulert scores pydantic 90/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 pydantic affected?

Yes. 2.14.1, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of pydantic should I use?

2.14.1 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 pydantic have?

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

1 vulnerability was recorded for pydantic in the last 12 months, and the oldest entry in this database dates to 13 May 2021. 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 pydantic 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 pydantic for upcoming vulnerabilities?

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