GHSA-9q2p-fj49-vpxj is a medium-severity (CVSS 5.3) vulnerability in marshmallow. A fix is available for marshmallow — see the affected versions and patch details below.
In marshmallow library the schema "only" option treats an empty list as implying no "only" option
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-9q2p-fj49-vpxj by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
marshmallow🐍marshmallowReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
In the marshmallow library before 2.15.1 and 3.x before 3.0.0b9 for Python, the schema "only" option treats an empty list as implying no "only" option, which allows a request that was intended to expose no fields to instead expose all fields (if the schema is being filtered dynamically using the "only" option, and there is a user role that produces an empty value for "only").
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | marshmallow | all versions | 2.15.1pip install --upgrade 'marshmallow==2.15.1' |
| 🐍PyPI | marshmallow | ≥ 3.0a0&&< 3.0.0b9 | 3.0.0b9pip install --upgrade 'marshmallow==3.0.0b9' |
Affected Products
marshmallowmarshmallow_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for marshmallow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update marshmallow to 2.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9q2p-fj49-vpxj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Frequently Asked Questions
Is GHSA-9q2p-fj49-vpxj in your dependencies?
Find it across PyPI, including transitive dependencies.