cve.bz

CVE-2026-108147 djangoproject django

6.9 mediumEPSS 0.6%Fix available

Medium (6.9) in djangoproject django. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.6% (unchanged from 0.6% a week ago) estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-108147 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-108147?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-108147?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-108147 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-108147

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-108147](https://cve.bz/cve/badge/CVE-2026-108147.svg)](https://cve.bz/cve/CVE-2026-108147)

HTML:

<a href="https://cve.bz/cve/CVE-2026-108147"><img src="https://cve.bz/cve/badge/CVE-2026-108147.svg" alt="CVE-2026-108147"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
djangoproject Djangofrom 6.1 before 6.1.3
djangoproject Djangofrom 6.0.4 before 6.0.10
djangoproject Djangofrom 5.2.13 before 5.2.19

Fixed in

ProductFixed in
djangoproject Django6.0
djangoproject Django5.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12python-django3:3.2.25-0+deb12u7DEBIAN-CVE-2026-108147
Debian13python-djangono fix listedDEBIAN-CVE-2026-108147
Debian14python-django3:5.2.19-1DEBIAN-CVE-2026-108147
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 5 morepython-djangono fix listedUBUNTU-CVE-2026-108147
openSUSELeap 16.0python-Django5.2.4-bp160.13.1openSUSE-SU-2026:22278-1
openSUSETumbleweedpython-Django6.1.3-1.1openSUSE-SU-2026:12518-1
openSUSETumbleweedpython-Django44.2.30-7.1openSUSE-SU-2026:12502-1
openSUSETumbleweedpython-Django55.2.19-1.1openSUSE-SU-2026:12519-1
Alpinev3.24py3-django5.2.19-r0ALPINE-CVE-2026-108147

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpine.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON