Django
Library41.1Mdownloads / month
PyPI downloads, last 30 days (pypistats, mirrors excluded).
PyPI ↗ · as of 2 Nov 2026 · High confidence
Version split: unknown. No public source for this product.
CVE-2026-108147
Potential memory exhaustion in MultiPartParser via base64-encoded file upload
No known exploitation. EPSS puts it in the 48th percentile. Fixed versions are out.
CVSS 3.15.3MediumEPSS percentile48th0.6% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix1 product5 fixed builds listed below
No public exploit knownFix1 product5 fixed builds listed below
Check it yourself
Run the check e.g. OID 1.3.6.1.4.1.25623.1.0.180977
What to do
Find your product and version, then upgrade to the build on the right.
- djangoproject DjangoAffected: ≥ 6.1, < 6.1.3Upgrade to: 6.1.3Affected: ≥ 6.0.4, < 6.0.10Upgrade to: 6.0.10Affected: ≥ 5.2.13, < 5.2.19Upgrade to: 5.2.19Fixed builds6.0, 5.2Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
An issue was discovered in Django 6.1 before 6.1.3, 6.0.4 before 6.0.10, and 5.2.13 before 5.2.19. `django.http.multipartparser.MultiPartParser` is subject to excessive memory consumption when processing multipart file uploads with base64 `Content-Transfer-Encoding`, which could be buffered entirely in memory before being passed to upload handlers. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Ignacy Kujawa for reporting this issue.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
EPSS48th
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.6% chance of exploitation activity in the next 30 days, which ranks it in the 48th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
5 events over 6 days, from the signal feeds we watch.
- OpenVAS check added
- Publishedweakness classified, att&ck mapped, record updated
Affected products
Scale
How widely the affected products are used. This is not a count of vulnerable hosts.
Estimate Public sources, each figure dated. How much of it is already patched is not known.
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Scored 5.3 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity NoneNo integrity impact
- Availability LowReduced performance or intermittent disruption of service
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Django, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI