CVE-2026-108147: djangoproject Django · Unthrottled Resource Allocation
Affects djangoproject DjangoSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium · fixed in 6.1.3 : update djangoproject Django when convenient.
Data as of 3 Nov 2026, 16:13 UTC
Thin evidence
One scorer or none| CNA (DSF) | CVSS 3.1 | 5.3 |
|---|---|---|
| CNA (DSF) | CVSS 4.0 | 6.9 |
- Patch
- Available – fixed in 6.1.3, 6.0.10, 5.2.19
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade Django and django to 6.1.3, 6.0.10 or 5.2.19.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Djangodjango | Affected
| Fixed in
|
| Djangodjango | Affected
| Fixed in
|
| Djangodjango | Affected
| Fixed in
|
PyPIdjangopkg:pypi/djangoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- docs.djangoproject.com/en/dev/releases/security/ (opens in a new tab)
- groups.google.com/g/django-announce (opens in a new tab)
- github.com/django/django/commit/5d95d9236fa4ededfb1931c60a65432385ece85f (opens in a new tab)
- github.com/django/django/commit/8b435411f11d69a0dd41a8837654323502e6058e (opens in a new tab)
- github.com/django/django/commit/a29ee4a55acedbe7ba0cb4d2db28c4e4d2848e02 (opens in a new tab)
- github.com/django/django/commit/4bd1f59a80adafddbd47527c66d92d6a224244d8 (opens in a new tab)
- djangoproject.com/weblog/2026/nov/03/security-releases/ (opens in a new tab)