CVE-2019-9710: An issue was discovered in webargs before 5.1.3, as used with marshmallow and other products

Q: How do I fix CVE-2019-9710?

webargs: upgrade to 5.1.3. Exact commands for each OS are on this page.

Q: Is CVE-2019-9710 being exploited?

CVE-2019-9710 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-9710 affect?

CVE-2019-9710 affects webargs. Severity is high (CVSS 8.1). An issue was discovered in webargs before 5.1.3, as used with marshmallow and other products. JSON parsing uses a short-lived cache to store the parsed JSON body. This cache is not thread-safe, meaning that incorrect JSON payloads could hav

Q: How urgent is CVE-2019-9710?

Priority 55/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 8.1REMOTEUPGRADE

CVE-2019-9710 is a high-severity flaw (CVSS 8.1) affecting webargs. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in webargs before 5.1.3, as used with marshmallow and other products. JSON parsing uses a short-lived cache to store the parsed JSON body. This cache is not thread-safe, meaning that incorrect JSON payloads could have been parsed for concurrent requests.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	1.1% (top 34%)
CISA exploited list	No
Weakness	CWE-362
Published	2019-03-12
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: webargs project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-03-12 02:29 UTCPublished CVE record published
2026-06-17 02:44 UTCUpdated Record last modified

webargs project webargs UPGRADE

Affected: < 5.1.3

Fixed in: 5.1.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy webargs || rpm -q webargs || webargs --version

2. UPGRADE to 5.1.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade webargs

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade webargs

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-9710?

webargs: upgrade to 5.1.3. Exact commands for each OS are on this page.

Is CVE-2019-9710 being exploited?

CVE-2019-9710 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-9710 affect?

CVE-2019-9710 affects webargs. Severity is high (CVSS 8.1). An issue was discovered in webargs before 5.1.3, as used with marshmallow and other products. JSON parsing uses a short-lived cache to store the parsed JSON body. This cache is not thread-safe, meaning that incorrect JSON payloads could hav

How urgent is CVE-2019-9710?

Priority 55/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2020-7965 HIGH 8.8 UPGRADE flaskparser.py in Webargs 5.x through 5.5.2 doesn't check that the Content-Type header is application/json whe

References

← Back to latest CVEs