VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

multidict: vulnerability history, versions and safety

multidict is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 4 releases, first recorded in Oct 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
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all multidict vulnerabilities

Vulert verdict on multidict 7.1.0 i

Updated on 23 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 7.1.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Depended on by 48,600 packages i
  • Stars 495 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 multidict, 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
7.1.0 09 Oct 2026 none Apache-2.0 — Details →
7.0.0 26 Sep 2026 none Apache-2.0 — Details →
6.9.1 21 Sep 2026 none Apache-2.0 — Details →
6.9.0 18 Sep 2026 M1 U1 Apache-2.0 Yes Details →
6.8.0 09 Sep 2026 M1 U1 Apache-2.0 Yes Details →
6.7.1 26 Jan 2026 M1 U1 Apache-2.0 Yes Details →
6.7.0 06 Oct 2025 M1 U1 Apache-2.0 Yes Details →
6.6.4 11 Aug 2025 none Apache-2.0 — Details →
6.6.3 30 Jun 2025 none Apache-2.0 — Details →
6.6.2 28 Jun 2025 none Apache-2.0 — Details →
6.6.1 28 Jun 2025 none Apache-2.0 — Details →
6.6.0 27 Jun 2025 none Apache-2.0 — Details →
6.5.1 24 Jun 2025 none Apache-2.0 — Details →
6.5.0 17 Jun 2025 none Apache-2.0 — Details →
6.4.4 19 May 2025 none Apache-2.0 — Details →
6.4.3 10 Apr 2025 none Apache-2.0 — Details →
6.4.2 09 Apr 2025 none Apache-2.0 — Details →
6.4.1 09 Apr 2025 none Apache-2.0 — Details →
6.4.0 09 Apr 2025 none Apache-2.0 — Details →
6.3.2 03 Apr 2025 none Apache-2.0 — Details →
6.3.1 01 Apr 2025 none Apache-2.0 — Details →
6.3.0 31 Mar 2025 none Apache-2.0 — Details →
6.2.0 17 Mar 2025 none Apache-2.0 — Details →
6.1.0 09 Sep 2024 none Apache-2.0 — Details →
6.0.5 01 Feb 2024 none Apache-2.0 — Details →
6.0.4 24 Dec 2022 none Apache-2.0 — Details →
6.0.3 03 Dec 2022 none Apache-2.0 — Details →
6.0.2 24 Jan 2022 none Apache-2.0 — Details →
6.0.1 23 Jan 2022 none Apache-2.0 — Details →
6.0.0 22 Jan 2022 none Apache-2.0 — Details →
5.2.0 03 Oct 2021 none Apache-2.0 — Details →
5.2.0a25 03 Oct 2021 none Apache-2.0 — Details →
5.2.0a24 03 Oct 2021 none Apache-2.0 — Details →
5.2.0a15 02 Oct 2021 none Apache-2.0 — Details →
5.2.0a12 02 Oct 2021 none Apache-2.0 — Details →
5.2.0a6 30 Sep 2021 none Apache-2.0 — Details →
5.2.0a0 30 Sep 2021 none Apache-2.0 — Details →
5.1.0 03 Dec 2020 none Apache-2.0 — Details →
5.0.2 14 Nov 2020 none Apache-2.0 — Details →
5.0.1 14 Nov 2020 none Apache-2.0 — Details →
5.0.0 12 Oct 2020 none Apache-2.0 — Details →
4.7.6 14 May 2020 none Apache-2.0 — Details →
4.7.5 21 Feb 2020 none Apache-2.0 — Details →
4.7.4 11 Jan 2020 none Apache-2.0 — Details →
4.7.3 30 Dec 2019 none Apache-2.0 — Details →
4.7.2 20 Dec 2019 none Apache-2.0 — Details →
4.7.1 11 Dec 2019 none Apache-2.0 — Details →
4.7.0 10 Dec 2019 none Apache-2.0 — Details →
4.6.1 21 Nov 2019 none Apache-2.0 — Details →
4.6.0 20 Nov 2019 none Apache-2.0 — Details →
4.6.0a3 20 Nov 2019 none Apache-2.0 — Details →
4.6.0a2 19 Nov 2019 none Apache-2.0 — Details →
4.5.2 28 Nov 2018 none Apache-2.0 — Details →
4.5.1 22 Nov 2018 none Apache-2.0 — Details →
4.5.0 19 Nov 2018 none Apache-2.0 — Details →
4.4.2 18 Sep 2018 none Apache-2.0 — Details →
4.4.1 17 Sep 2018 none Apache-2.0 — Details →
4.4.0 03 Sep 2018 none Apache-2.0 — Details →
4.4.0a42 03 Sep 2018 none Apache-2.0 — Details →
4.4.0a40 03 Sep 2018 none Apache-2.0 — Details →
4.4.0a39 25 Aug 2018 none Apache-2.0 — Details →
4.4.0a38 13 Aug 2018 none Apache-2.0 — Details →
4.4.0a37 13 Aug 2018 none Apache-2.0 — Details →
4.4.0a36 13 Aug 2018 none Apache-2.0 — Details →
4.4.0a35 13 Aug 2018 none Apache-2.0 — Details →
4.4.0a33 13 Aug 2018 none Apache-2.0 — Details →
4.4.0a32 13 Aug 2018 none Apache-2.0 — Details →
4.4.0a31 13 Aug 2018 none Apache-2.0 — Details →
4.4.0a30 13 Aug 2018 none Apache-2.0 — Details →
4.4.0a34 13 Aug 2018 none Apache-2.0 — Details →
4.4.0a29 12 Aug 2018 none Apache-2.0 — Details →
4.4.0a28 12 Aug 2018 none Apache-2.0 — Details →
4.4.0a27 12 Aug 2018 none Apache-2.0 — Details →
4.4.0a26 12 Aug 2018 none Apache-2.0 — Details →
4.4.0a25 12 Aug 2018 none Apache-2.0 — Details →
4.4.0a24 12 Aug 2018 none Apache-2.0 — Details →
4.4.0a23 12 Aug 2018 none Apache-2.0 — Details →
4.4.0a22 12 Aug 2018 none Apache-2.0 — Details →
4.4.0a20 12 Aug 2018 none Apache-2.0 — Details →
4.4.0a21 12 Aug 2018 none Apache-2.0 — Details →
4.4.0a19 12 Aug 2018 none Apache-2.0 — Details →
4.4.0a16 12 Aug 2018 none Apache-2.0 — Details →
4.4.0a18 12 Aug 2018 none Apache-2.0 — Details →
4.4.0a17 12 Aug 2018 none Apache-2.0 — Details →
4.4.0a12 11 Aug 2018 none Apache-2.0 — Details →
4.4.0a15 11 Aug 2018 none Apache-2.0 — Details →
4.4.0a14 11 Aug 2018 none Apache-2.0 — Details →
4.4.0a13 11 Aug 2018 none Apache-2.0 — Details →
4.4.0a11 11 Aug 2018 none Apache-2.0 — Details →
4.4.0a10 11 Aug 2018 none Apache-2.0 — Details →
4.4.0a9 11 Aug 2018 none Apache-2.0 — Details →
4.4.0a8 11 Aug 2018 none Apache-2.0 — Details →
4.4.0a7 10 Aug 2018 none Apache-2.0 — Details →
4.4.0a6 10 Aug 2018 none Apache-2.0 — Details →
4.4.0a5 09 Aug 2018 none Apache-2.0 — Details →
4.4.0a4 06 Aug 2018 none Apache-2.0 — Details →
4.4.0a3 02 Aug 2018 none Apache-2.0 — Details →
4.4.0a2 02 Aug 2018 none Apache-2.0 — Details →
4.4.0a1 01 Aug 2018 none Apache-2.0 — Details →
4.4.0a0 01 Aug 2018 none Apache-2.0 — Details →
4.3.1 06 May 2018 none — — Details →
4.3.0 06 May 2018 none — — Details →
4.2.0 15 Apr 2018 none — — Details →
4.1.0 28 Jan 2018 none — — Details →
4.0.0 14 Jan 2018 none — — Details →
3.3.2 02 Nov 2017 none — — Details →
3.3.1 02 Nov 2017 none — — Details →
3.3.0 15 Oct 2017 none — — Details →
3.2.1a0 03 Oct 2017 none — — Details →
3.2.0 17 Sep 2017 none — — Details →
3.2.0a3 16 Sep 2017 none — — Details →
3.1.4a3 25 Jul 2017 none — — Details →
3.1.4a2 25 Jul 2017 none — — Details →
3.1.4a1 25 Jul 2017 none — — Details →
3.1.3 14 Jul 2017 none — — Details →
3.1.3a0 14 Jul 2017 none — — Details →
3.1.1 08 Jul 2017 none — — Details →
3.1.0 25 Jun 2017 none — — Details →
3.0.0 21 Jun 2017 none — — Details →
2.1.6 28 May 2017 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for multidict

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-104874: Multidict Memory Leak in Items-View Operations 5.3 medium 6.9.1 05 Oct 2026
CVE-2026-104874: Multidict Memory Leak in Items-View Union and Subtraction 5.3 medium 6.9.1 15 Oct 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 multidict

Is multidict safe to use?

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

Vulert scores multidict 84/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 multidict affected?

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

7.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 multidict have?

2 vulnerabilities are recorded for multidict 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 multidict vulnerabilities disclosed?

2 vulnerabilities were recorded for multidict in the last 12 months, and the oldest entry in this database dates to 05 Oct 2026. 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 multidict 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 multidict for upcoming vulnerabilities?

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