CVE-2026-108147

Potential memory exhaustion in MultiPartParser via base64-encoded file upload

  • Medium 6.9

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.

Key facts

Published
3 Nov 2026
Last changed
3 Nov 2026
Assigned by
DSF
EPSS
0.579% likely to be exploited in the next 30 days, higher than 48.234% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.3CVSS 3.1, Mediumfrom the CNA (DSF)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
  • 6.9CVSS 4.0, Mediumfrom the CNA (DSF)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

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

CAPEC-130: Excessive Allocation (CNA impact statement)

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
djangoprojectDjango
  • Default status: unaffected
  • 6.1 up to but excluding 6.1.3 (affected)
  • 6.1.3 (unaffected)
  • 6.0 up to but excluding 6.0.4 (unaffected)
  • 6.0.4 up to but excluding 6.0.10 (affected)
  • 6.0.10 (unaffected)
  • 5.2 up to but excluding 5.2.13 (unaffected)
  • 5.2.13 up to but excluding 5.2.19 (affected)
  • 5.2.19 (unaffected)

Timeline

  1. 7 Sep 2026 Initial report received.
  2. 15 Oct 2026 Vulnerability confirmed.
  3. 3 Nov 2026 Security release issued.
  4. 3 Nov 2026 Published

Weakness

References