CVE-2015-0846 is a high-severity (CVSS 7.5) Information Exposure vulnerability in django-markupfield. A fix is available for django-markupfield — see the affected versions and patch details below.
django-markupfield Arbitrary File Read
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-markupfieldReal-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
django-markupfield before 1.3.2 uses the default docutils RESTRUCTUREDTEXT_FILTER_SETTINGS settings, which allows remote attackers to include and read arbitrary files via unspecified vectors.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django-markupfield | all versions | 1.3.2pip install --upgrade 'django-markupfield==1.3.2' |
Affected Products
django-markupfielddjango-markupfield_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django-markupfield, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update django-markupfield to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-0846 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2015-0846 in your dependencies?
Find it across PyPI, including transitive dependencies.