Vulnerability Database · PyPI · webargs · Version
webargs 2.1.0
2.1.0 is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 8.7.1.
Critical 0 High 1 Medium 0 Low 0 Unrated 2
-
Released 01 Apr 2018
Licence MIT
Also known from other sources 2
Newer releases 104
Database updated 23/Oct/2026
Release and licence data published by PyPI. 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 Vulnerabilities affecting this version
webargs 2.1.0 vulnerabilities
3 vulnerabilities cover webargs 2.1.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| 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-2019-9710: webargs - JSON Parsing Cache Thread-Safety Issue | N/A unrated | 5.1.3 | 12 Mar 2019 |
Looking for another version, or everything Vulert holds for webargs?
Questions
About webargs 2.1.0
Is webargs 2.1.0 vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover webargs 2.1.0: 0 critical, 1 high, 0 medium and 0 low, plus 2 not yet rated. The upgrade Vulert recommends is 8.7.1, and each entry above names the fixed version to move to.
Which version of webargs should I use instead of 2.1.0?
8.7.1 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 2.1.0 the latest release of webargs?
No. 2.1.0 was published 01 Apr 2018, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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.