VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

webargs: vulnerability history, versions and safety

webargs is a package in the PyPI ecosystem. Vulert records 5 vulnerabilities for it across 79 releases, from Mar 2019 to Apr 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H2 U3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all webargs vulnerabilities

Vulert verdict on webargs 8.7.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 8.7.1 — unaffected i
  • Vulnerabilities on record 5 over 2 years · 0 in the last year i
  • Latest disclosure 07 Apr 2021 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 331 packages i
  • Stars 1,411 i
  • OpenSSF scorecard 5/10 i
  • Last release 11 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 webargs, 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
8.7.1 29 Oct 2025 none MIT — Details →
8.7.0 18 Apr 2025 none MIT — Details →
8.6.0 11 Sep 2024 none MIT — Details →
8.4.0 07 Jan 2024 none MIT — Details →
8.3.0 10 Jul 2023 none MIT — Details →
8.2.0 12 Jul 2022 none MIT — Details →
8.1.0 12 Jan 2022 none MIT — Details →
8.0.1 12 Aug 2021 none MIT — Details →
8.0.0 08 Apr 2021 none MIT — Details →
7.0.1 14 Dec 2020 none MIT — Details →
7.0.0 10 Dec 2020 none MIT — Details →
7.0.0b2 02 Dec 2020 none MIT — Details →
7.0.0b1 11 Sep 2020 none MIT — Details →
6.1.1 08 Sep 2020 none MIT — Details →
6.1.0 05 May 2020 none MIT — Details →
6.0.0 27 Feb 2020 none MIT — Details →
6.0.0b8 16 Feb 2020 none MIT — Details →
6.0.0b7 14 Feb 2020 none MIT — Details →
6.0.0b6 31 Jan 2020 none MIT — Details →
6.0.0b5 30 Jan 2020 none MIT — Details →
6.0.0b4 29 Jan 2020 none MIT — Details →
5.5.3 29 Jan 2020 none MIT — Details →
6.0.0b3 21 Jan 2020 none MIT — Details →
6.0.0b2 07 Jan 2020 none MIT — Details →
6.0.0b1 06 Jan 2020 none MIT — Details →
5.5.2 06 Oct 2019 H1 U1 MIT Yes Details →
5.5.1 15 Sep 2019 H1 U1 MIT Yes Details →
5.5.0 07 Sep 2019 H1 U1 MIT Yes Details →
5.4.0 24 Jul 2019 H1 U1 MIT Yes Details →
5.3.2 19 Jun 2019 H1 U1 MIT Yes Details →
5.3.1 05 May 2019 H1 U1 MIT Yes Details →
5.3.0 09 Apr 2019 H1 U1 MIT Yes Details →
5.2.0 16 Mar 2019 H1 U1 MIT Yes Details →
5.1.3 11 Mar 2019 H1 U1 MIT Yes Details →
5.1.2 04 Feb 2019 H2 U3 MIT Yes Details →
5.1.1.post0 31 Jan 2019 H2 U3 MIT Yes Details →
5.1.1 28 Jan 2019 H2 U3 MIT Yes Details →
5.1.0 11 Jan 2019 H2 U3 MIT Yes Details →
5.0.0 03 Jan 2019 H2 U3 MIT Yes Details →
4.4.1 03 Jan 2019 H1 U2 MIT Yes Details →
4.4.0 03 Jan 2019 H1 U2 MIT Yes Details →
4.3.1 01 Jan 2019 H1 U2 MIT Yes Details →
4.3.0 30 Dec 2018 H1 U2 MIT Yes Details →
4.2.0 27 Dec 2018 H1 U2 MIT Yes Details →
4.1.3 02 Dec 2018 H1 U2 MIT Yes Details →
4.1.2 03 Nov 2018 H1 U2 MIT Yes Details →
4.1.1 25 Oct 2018 H1 U2 MIT Yes Details →
4.1.0 18 Sep 2018 H1 U2 MIT Yes Details →
4.0.0 16 Jul 2018 H1 U2 MIT Yes Details →
3.0.2 06 Jul 2018 H1 U2 MIT Yes Details →
3.0.1 07 Jun 2018 H1 U2 MIT Yes Details →
3.0.0 06 May 2018 H1 U2 MIT Yes Details →
2.1.0 01 Apr 2018 H1 U2 MIT Yes Details →
2.0.0 09 Feb 2018 H1 U2 MIT Yes Details →
1.10.0 09 Feb 2018 H1 U2 MIT Yes Details →
1.9.0 03 Feb 2018 H1 U2 MIT Yes Details →
1.8.1 19 Jul 2017 H1 U2 MIT Yes Details →
1.8.0 17 Jul 2017 H1 U2 MIT Yes Details →
1.7.0 04 Jun 2017 H1 U2 MIT Yes Details →
1.6.3 18 May 2017 H1 U2 MIT Yes Details →
1.6.2 17 May 2017 H1 U2 MIT Yes Details →
1.6.1 01 May 2017 H1 U2 MIT Yes Details →
1.6.0 15 Mar 2017 H1 U2 MIT Yes Details →
1.5.3 04 Feb 2017 H1 U2 MIT Yes Details →
1.5.2 09 Jan 2017 H1 U2 MIT Yes Details →
1.5.1 28 Nov 2016 H1 U2 non-standard Yes Details →
1.5.0 22 Nov 2016 H1 U2 non-standard Yes Details →
1.4.0 30 Sep 2016 H1 U2 non-standard Yes Details →
1.3.4 11 Jun 2016 H1 U2 non-standard Yes Details →
1.3.3 30 May 2016 H1 U2 non-standard Yes Details →
1.3.2 14 Apr 2016 H1 U2 non-standard Yes Details →
1.3.1 13 Apr 2016 H1 U2 non-standard Yes Details →
1.3.0 05 Apr 2016 H1 U2 non-standard Yes Details →
1.2.0 05 Jan 2016 H1 U2 non-standard Yes Details →
1.1.1 14 Nov 2015 H1 U2 non-standard Yes Details →
1.1.0 09 Nov 2015 H1 U2 non-standard Yes Details →
1.0.0 20 Oct 2015 H1 U2 non-standard Yes Details →
0.18.0 04 Oct 2015 H1 U2 non-standard Yes Details →
0.17.0 30 Sep 2015 H1 U2 non-standard Yes Details →
0.16.0 27 Sep 2015 H1 U2 non-standard Yes Details →
0.15.0 22 Aug 2015 H1 U2 non-standard Yes Details →
0.14.0 28 Jun 2015 H1 U2 non-standard Yes Details →
0.13.0 05 Apr 2015 H1 U2 non-standard Yes Details →
0.12.0 22 Mar 2015 H1 U2 non-standard Yes Details →
0.11.0 02 Mar 2015 H1 U2 non-standard Yes Details →
0.10.0 24 Dec 2014 H1 U2 non-standard Yes Details →
0.9.1 12 Dec 2014 H1 U2 non-standard Yes Details →
0.9.0 09 Dec 2014 H1 U2 non-standard Yes Details →
0.8.1 29 Oct 2014 H1 U2 non-standard Yes Details →
0.8.0 26 Oct 2014 H1 U2 non-standard Yes Details →
0.7.0 18 Oct 2014 H1 U2 non-standard Yes Details →
0.6.2 05 Oct 2014 H1 U2 non-standard Yes Details →
0.6.1 28 Sep 2014 H1 U2 non-standard Yes Details →
0.6.0 23 Sep 2014 H1 U2 non-standard Yes Details →
0.5.1 31 Aug 2014 H1 U2 non-standard Yes Details →
0.5.0 27 Jul 2014 H1 U2 non-standard Yes Details →
0.4.0 05 Jun 2014 H1 U2 non-standard Yes Details →
0.3.4 27 Apr 2014 H1 U2 non-standard Yes Details →
0.3.3 21 Mar 2014 H1 U2 non-standard Yes Details →
0.3.2 04 Mar 2014 H1 U2 non-standard Yes Details →
0.3.1 03 Mar 2014 H1 U2 — Yes Details →
0.3.0 02 Mar 2014 H1 U2 — Yes Details →
0.2.0 26 Feb 2014 H1 U2 — Yes Details →
0.1.0 17 Feb 2014 H1 U2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 3
  • 2020 1
  • 2021 1

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

03 Vulnerabilities

Recorded vulnerabilities for webargs

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-7965: Cross-Site Request Forgery in Webargs 8.8 high 5.5.3 07 Apr 2021
CVE-2019-9710: webargs - JSON Parsing Cache Thread-Safety Vulnerability 8.1 high 5.1.3 12 Mar 2019
CVE-2019-9710: webargs - Thread-Safety Issue in JSON Parsing N/A unrated 5.1.3 12 Mar 2019
CVE-2020-7965: Webargs JSON Request Validation Bypass N/A unrated 5.5.3 29 Jan 2020
CVE-2019-9710: webargs - JSON Parsing Cache Thread-Safety Issue N/A unrated 5.1.3 12 Mar 2019

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 webargs

Is webargs safe to use?

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

Vulert scores webargs 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 webargs affected?

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

8.7.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 webargs have?

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

0 vulnerabilities were recorded for webargs in the last 12 months, and the oldest entry in this database dates to 12 Mar 2019. 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 webargs 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 webargs for upcoming vulnerabilities?

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