VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

marshmallow: vulnerability history, versions and safety

marshmallow is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 73 releases, from Sep 2018 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
2 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 marshmallow vulnerabilities

Vulert verdict on marshmallow 4.3.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 4.3.1 — unaffected i
  • Vulnerabilities on record 4 over 7 years · 2 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Depended on by 1,703 packages i
  • Stars 7,246 i
  • OpenSSF scorecard 6/10 i
  • Last release 2 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 marshmallow, 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
4.3.1 08 Aug 2026 none MIT — Details →
4.3.0 03 Apr 2026 none MIT — Details →
4.2.4 02 Apr 2026 none MIT — Details →
4.2.3 25 Mar 2026 none MIT — Details →
4.2.2 04 Feb 2026 none MIT — Details →
4.2.1 23 Jan 2026 none MIT — Details →
4.2.0 04 Jan 2026 none MIT — Details →
3.26.2 22 Dec 2025 none MIT — Details →
4.1.2 22 Dec 2025 none MIT — Details →
4.1.1 05 Dec 2025 U1 MIT Yes Details →
4.1.0 01 Nov 2025 U1 MIT Yes Details →
4.0.1 28 Aug 2025 U1 MIT Yes Details →
4.0.0 17 Apr 2025 U1 MIT Yes Details →
3.26.1 03 Feb 2025 M1 U1 MIT Yes Details →
3.26.0 23 Jan 2025 M1 U1 MIT Yes Details →
3.25.1 11 Jan 2025 M1 U1 MIT Yes Details →
3.25.0 09 Jan 2025 M1 U1 MIT Yes Details →
3.24.2 08 Jan 2025 M1 U1 MIT Yes Details →
3.24.1 07 Jan 2025 M1 U1 MIT Yes Details →
3.24.0 06 Jan 2025 M1 U1 MIT Yes Details →
3.23.3 03 Jan 2025 M1 U1 MIT Yes Details →
3.23.2 19 Dec 2024 M1 U1 MIT Yes Details →
3.23.1 01 Nov 2024 M1 U1 MIT Yes Details →
3.23.0 17 Oct 2024 M1 U1 MIT Yes Details →
3.22.0 20 Aug 2024 M1 U1 MIT Yes Details →
3.21.3 06 Jun 2024 M1 U1 MIT Yes Details →
3.21.2 01 May 2024 M1 U1 MIT Yes Details →
3.21.1 04 Mar 2024 M1 U1 MIT Yes Details →
3.21.0 26 Feb 2024 M1 U1 MIT Yes Details →
3.20.2 09 Jan 2024 M1 U1 MIT Yes Details →
3.20.1 20 Jul 2023 M1 U1 MIT Yes Details →
3.20.0 20 Jul 2023 M1 U1 MIT Yes Details →
3.19.0 11 Nov 2022 M1 U1 MIT Yes Details →
3.18.0 15 Sep 2022 M1 U1 MIT Yes Details →
3.17.1 22 Aug 2022 M1 U1 MIT Yes Details →
3.17.0 26 Jun 2022 M1 U1 MIT Yes Details →
3.16.0 29 May 2022 M1 U1 MIT Yes Details →
3.15.0 12 Mar 2022 M1 U1 MIT Yes Details →
3.14.1 15 Nov 2021 M1 U1 MIT Yes Details →
3.14.0 17 Oct 2021 M1 U1 MIT Yes Details →
3.13.0 21 Jul 2021 M1 U1 MIT Yes Details →
3.12.2 06 Jul 2021 M1 U1 MIT Yes Details →
3.12.1 10 May 2021 M1 U1 MIT Yes Details →
3.12.0 10 May 2021 M1 U1 MIT Yes Details →
3.11.1 30 Mar 2021 M1 U1 MIT Yes Details →
3.11.0 28 Mar 2021 M1 U1 MIT Yes Details →
3.10.0 19 Dec 2020 M1 U1 MIT Yes Details →
3.9.1 08 Nov 2020 M1 U1 MIT Yes Details →
3.9.0 31 Oct 2020 M1 U1 MIT Yes Details →
3.8.0 16 Sep 2020 M1 U1 MIT Yes Details →
3.7.1 20 Jul 2020 M1 U1 MIT Yes Details →
3.7.0 09 Jul 2020 M1 U1 MIT Yes Details →
3.6.1 02 Jun 2020 M1 U1 MIT Yes Details →
3.6.0 08 May 2020 M1 U1 MIT Yes Details →
3.5.2 30 Apr 2020 M1 U1 MIT Yes Details →
3.5.1 05 Mar 2020 M1 U1 MIT Yes Details →
2.21.0 05 Mar 2020 none MIT — Details →
3.5.0 19 Feb 2020 M1 U1 MIT Yes Details →
3.4.0 02 Feb 2020 M1 U1 MIT Yes Details →
3.3.0 06 Dec 2019 M1 U1 MIT Yes Details →
3.2.2 04 Nov 2019 M1 U1 MIT Yes Details →
3.2.1 01 Oct 2019 M1 U1 MIT Yes Details →
3.2.0 17 Sep 2019 M1 U1 MIT Yes Details →
3.1.1 16 Sep 2019 M1 U1 MIT Yes Details →
3.1.0 15 Sep 2019 M1 U1 MIT Yes Details →
2.20.5 15 Sep 2019 none MIT — Details →
3.0.5 13 Sep 2019 M1 U1 MIT Yes Details →
3.0.4 12 Sep 2019 M1 U1 MIT Yes Details →
2.20.4 12 Sep 2019 none MIT — Details →
3.0.3 05 Sep 2019 M1 U1 MIT Yes Details →
3.0.2 04 Sep 2019 M1 U1 MIT Yes Details →
2.20.3 04 Sep 2019 none MIT — Details →
3.0.1 21 Aug 2019 M1 U1 MIT Yes Details →
2.20.2 20 Aug 2019 none MIT — Details →
3.0.0 18 Aug 2019 M1 U1 MIT Yes Details →
2.20.1 13 Aug 2019 none MIT — Details →
2.20.0 10 Aug 2019 none MIT — Details →
3.0.0rc9 31 Jul 2019 M1 U1 MIT Yes Details →
3.0.0rc8 04 Jul 2019 M1 U1 MIT Yes Details →
2.19.5 18 Jun 2019 none MIT — Details →
2.19.4 17 Jun 2019 none MIT — Details →
3.0.0rc7 15 Jun 2019 M1 U1 MIT Yes Details →
2.19.3 15 Jun 2019 none MIT — Details →
3.0.0rc6 05 May 2019 M1 U1 MIT Yes Details →
3.0.0rc5 30 Mar 2019 M1 U1 MIT Yes Details →
2.19.2 30 Mar 2019 none MIT — Details →
2.19.1 16 Mar 2019 none MIT — Details →
2.19.0 08 Mar 2019 none MIT — Details →
2.18.1 15 Feb 2019 none MIT — Details →
3.0.0rc4 08 Feb 2019 M1 U1 MIT Yes Details →
3.0.0rc3 14 Jan 2019 M1 U1 MIT Yes Details →
2.18.0 14 Jan 2019 none MIT — Details →
3.0.0rc2 03 Jan 2019 M1 U1 MIT Yes Details →
2.17.0 26 Dec 2018 none MIT — Details →
3.0.0rc1 30 Nov 2018 M1 U1 MIT Yes Details →
3.0.0b20 02 Nov 2018 none MIT — Details →
2.16.3 02 Nov 2018 none MIT — Details →
2.16.2 31 Oct 2018 none MIT — Details →
3.0.0b19 25 Oct 2018 none MIT — Details →
2.16.1 23 Oct 2018 none MIT — Details →
3.0.0b18 16 Oct 2018 none — — Details →
3.0.0b17 13 Oct 2018 none — — Details →
2.16.0 11 Oct 2018 none — — Details →
2.15.6 21 Sep 2018 none — — Details →
3.0.0b16 21 Sep 2018 none — — Details →
3.0.0b15 19 Sep 2018 none — — Details →
3.0.0b14 15 Sep 2018 none — — Details →
2.15.5 15 Sep 2018 none — — Details →
3.0.0b13 04 Aug 2018 none — — Details →
2.15.4 04 Aug 2018 none — — Details →
3.0.0b12 05 Jul 2018 none — — Details →
3.0.0b11 20 May 2018 none — — Details →
2.15.3 20 May 2018 none — — Details →
3.0.0b10 11 May 2018 none — — Details →
2.15.2 11 May 2018 none — — Details →
3.0.0b9 26 Apr 2018 none — — Details →
2.15.1 26 Apr 2018 none — — Details →
3.0.0b8 24 Mar 2018 U1 — Yes Details →
3.0.0b7 03 Feb 2018 U1 — Yes Details →
3.0.0b6 12 Jan 2018 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2025 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for marshmallow

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-17175: Vulnerability in marshmallow Library 5.3 medium 2.15.1 10 Oct 2018
Denial of Service Vulnerability in Marshmallow Package 5.3 medium 3.26.2 22 Dec 2025
CVE-2025-68480: Marshmallow Denial of Service Vulnerability in Schema.load(many) 5.3 medium 3.26.2 07 Jul 2026
CVE-2018-17175: Vulnerability in marshmallow N/A unrated 2.15.1 18 Sep 2018

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 marshmallow

Is marshmallow safe to use?

Vulert records 4 vulnerabilities for marshmallow 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 marshmallow's Vulert package health score?

Vulert scores marshmallow 86/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 marshmallow affected?

No. 4.3.1, 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 marshmallow should I use?

4.3.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 marshmallow have?

4 vulnerabilities are recorded for marshmallow 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 marshmallow vulnerabilities disclosed?

2 vulnerabilities were recorded for marshmallow in the last 12 months, and the oldest entry in this database dates to 18 Sep 2018. 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 marshmallow 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 marshmallow for upcoming vulnerabilities?

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