CVE-2011-4104 is a critical-severity (CVSS 9.8) Improper Input Validation vulnerability in django-tastypie. A fix is available for django-tastypie — see the affected versions and patch details below.
Django Tastypie Improper Deserialization of YAML Data
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
django-tastypieReal-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
The from_yaml method in serializers.py in Django Tastypie before 0.9.10 does not properly deserialize YAML data, which allows remote attackers to execute arbitrary Python code via vectors related to the yaml.load method.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django-tastypie | all versions | 0.9.10pip install --upgrade 'django-tastypie==0.9.10' |
Affected Products
tastypiedjangoprojectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django-tastypie, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update django-tastypie to 0.9.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-4104 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is CVE-2011-4104 in your dependencies?
Find it across PyPI, including transitive dependencies.