VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

deepdiff: vulnerability history, versions and safety

deepdiff is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 39 releases, from Sep 2025 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 C1 H1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all deepdiff vulnerabilities

Vulert verdict on deepdiff 9.1.0 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 9.1.0 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 3 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Depended on by 1,238 packages i
  • Stars 2,537 i
  • Last release 5 months ago 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 deepdiff, 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
9.1.0 15 May 2026 none MIT — Details →
9.0.0 30 Mar 2026 none MIT — Details →
8.6.2 18 Mar 2026 none MIT — Details →
8.6.1 03 Sep 2025 H1 U1 MIT Yes Details →
8.6.0 08 Aug 2025 C1 H1 U2 MIT Yes Details →
8.5.0 09 May 2025 C1 H1 U2 MIT Yes Details →
8.4.2 17 Mar 2025 C1 H1 U2 MIT Yes Details →
8.4.1 17 Mar 2025 C1 H1 U2 MIT Yes Details →
8.4.0 16 Mar 2025 C1 H1 U2 MIT Yes Details →
8.3.0 06 Mar 2025 C1 H1 U2 MIT Yes Details →
8.2.0 04 Feb 2025 C1 H1 U2 MIT Yes Details →
8.1.1 16 Dec 2024 C1 H1 U2 MIT Yes Details →
8.1.0 16 Dec 2024 C1 H1 U2 MIT Yes Details →
8.0.1 28 Aug 2024 C1 H1 U2 MIT Yes Details →
8.0.0 27 Aug 2024 C1 H1 U2 MIT Yes Details →
7.0.1 08 Apr 2024 C1 H1 U2 MIT Yes Details →
7.0.0 08 Apr 2024 C1 H1 U2 MIT Yes Details →
6.7.1 14 Nov 2023 C1 H1 U2 MIT Yes Details →
6.7.0 08 Nov 2023 C1 H1 U2 MIT Yes Details →
6.6.1 17 Oct 2023 C1 H1 U2 MIT Yes Details →
6.6.0 04 Oct 2023 C1 H1 U2 MIT Yes Details →
6.5.0 12 Sep 2023 C1 H1 U2 MIT Yes Details →
6.4.1 01 Sep 2023 C1 H1 U2 MIT Yes Details →
6.4.0 01 Sep 2023 C1 H1 U2 MIT Yes Details →
6.3.1 06 Jul 2023 C1 H1 U2 MIT Yes Details →
6.3.0 17 Mar 2023 C1 H1 U2 MIT Yes Details →
6.2.3 06 Jan 2023 C1 H1 U2 MIT Yes Details →
6.2.2 11 Dec 2022 C1 H1 U2 MIT Yes Details →
6.2.1 18 Oct 2022 C1 H1 U2 MIT Yes Details →
5.8.1 13 May 2022 C1 H1 U2 MIT Yes Details →
5.8.0 10 Apr 2022 C1 H1 U2 MIT Yes Details →
5.7.0 17 Dec 2021 C1 H1 U2 MIT Yes Details →
5.6.0 13 Oct 2021 C1 H1 U2 MIT Yes Details →
5.5.0 29 Apr 2021 C1 H1 U2 MIT Yes Details →
5.3.0 16 Apr 2021 C1 H1 U2 MIT Yes Details →
5.2.3 16 Feb 2021 C1 H1 U2 MIT Yes Details →
5.2.2 15 Jan 2021 C1 H1 U2 MIT Yes Details →
5.2.1 01 Jan 2021 C1 H1 U2 MIT Yes Details →
5.2.0 01 Jan 2021 C1 H1 U2 MIT Yes Details →
5.0.2 24 Jul 2020 C1 H1 U2 MIT Yes Details →
5.0.1 01 Jul 2020 C1 H1 U2 MIT Yes Details →
5.0.0 23 Jun 2020 C1 H1 U2 MIT Yes Details →
4.3.2 19 Mar 2020 none MIT — Details →
4.3.1 11 Mar 2020 none MIT — Details →
4.3.0 10 Mar 2020 none MIT — Details →
4.2.0 30 Jan 2020 none MIT — Details →
4.0.9 08 Nov 2019 none MIT — Details →
4.0.8 18 Oct 2019 none MIT — Details →
4.0.7 12 Jul 2019 none MIT — Details →
4.0.6 13 Apr 2019 none MIT — Details →
4.0.5 07 Apr 2019 none MIT — Details →
4.0.4 05 Apr 2019 none MIT — Details →
4.0.2 24 Mar 2019 none MIT — Details →
3.3.0 30 Jun 2017 none MIT — Details →
3.2.1 29 May 2017 none MIT — Details →
3.2.0 12 Apr 2017 none MIT — Details →
3.1.2 10 Mar 2017 none MIT — Details →
3.1.1 04 Mar 2017 none MIT — Details →
3.1.0 31 Jan 2017 none MIT — Details →
3.0.0 27 Jan 2017 none MIT — Details →
2.5.3 05 Dec 2016 none MIT — Details →
2.5.2 05 Dec 2016 none MIT — Details →
2.5.1 18 Aug 2016 none MIT — Details →
2.5.0 18 Aug 2016 none MIT — Details →
2.1.2 09 Aug 2016 none MIT — Details →
2.1.1 08 Aug 2016 none MIT — Details →
2.1.0 08 Aug 2016 none MIT — Details →
2.0.0 07 Aug 2016 none MIT — Details →
1.8.0 06 Aug 2016 none MIT — Details →
1.7.0 03 Aug 2016 none MIT — Details →
1.6.0 31 Jul 2016 none MIT — Details →
1.5.0 02 Jul 2016 none MIT — Details →
1.2.0 12 Jun 2016 none MIT — Details →
1.1.0 27 Mar 2016 none MIT — Details →
1.0.2 25 Mar 2016 none MIT — Details →
1.0.1 15 Mar 2016 none MIT — Details →
1.0.0 27 Feb 2016 none MIT — Details →
0.6.1 15 Dec 2015 none MIT — Details →
0.6.0 03 Dec 2015 none MIT — Details →
0.5.9 03 Nov 2015 none MIT — Details →
0.5.8 02 Nov 2015 none MIT — Details →
0.5.7 11 Aug 2015 none MIT — Details →
0.5.5 26 Jul 2015 none MIT — Details →
0.5.4 24 Jul 2015 none MIT — Details →
0.5.3 22 Jul 2015 none MIT — Details →
0.5.2 20 Jul 2015 none MIT — Details →
0.5.1 20 Jul 2015 none MIT — Details →
0.5.0 20 Jul 2015 none MIT — Details →
0.2.0 25 Feb 2015 none MIT — Details →
0.1.1 27 Sep 2014 none MIT — Details →
0.1.0 27 Sep 2014 none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for deepdiff

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-58367: DeepDiff Class Pollution Vulnerability Leading to DoS and Remote Code Execution 10.0 critical 8.6.1 03 Sep 2025
CVE-2025-58367: DeepDiff Class Pollution Vulnerability Leading to DoS and RCE 10.0 critical 8.6.1 29 Jun 2026
CVE-2026-33155: DeepDiff Memory Exhaustion DoS via Unsafe Pickle Handling 8.7 high 8.6.2 18 Mar 2026
CVE-2026-33155: DeepDiff Memory Exhaustion DoS Vulnerability 8.7 high 8.6.2 13 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 deepdiff

Is deepdiff safe to use?

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

Vulert scores deepdiff 78/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 deepdiff affected?

No. 9.1.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 deepdiff should I use?

9.1.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 deepdiff have?

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

3 vulnerabilities were recorded for deepdiff in the last 12 months, and the oldest entry in this database dates to 03 Sep 2025. 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 deepdiff 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 deepdiff for upcoming vulnerabilities?

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