Skip to main content

Python EUVDEUVD-2026-19648

| CVE-2026-33034 HIGH
Allocation of Resources Without Limits or Throttling (CWE-770)
2026-04-07 DSF GHSA-933h-hp56-hf7m
7.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
SUSE
HIGH
qualitative
Red Hat
5.3 MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

4
Patch released
Apr 07, 2026 - 21:31 nvd
Patch available
EUVD ID Assigned
Apr 07, 2026 - 15:00 euvd
EUVD-2026-19648
Analysis Generated
Apr 07, 2026 - 15:00 vuln.today
CVE Published
Apr 07, 2026 - 14:22 nvd
HIGH 7.5

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 16 pypi packages depend on django (16 direct, 0 indirect)

Ecosystem-wide dependent count for version 6.0.

DescriptionCVE.org

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGI requests with a missing or understated Content-Length header could bypass the DATA_UPLOAD_MAX_MEMORY_SIZE limit when reading HttpRequest.body, allowing remote attackers to load an unbounded request body into memory. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Superior for reporting this issue.

AnalysisAI

Unbounded memory consumption in Django ASGI applications allows unauthenticated remote attackers to bypass DATA_UPLOAD_MAX_MEMORY_SIZE protections via malformed Content-Length headers, leading to denial of service. Affects Django 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. CVSS 7.5 (High) with network-accessible, low-complexity attack vector requiring no privileges. EPSS data not available; no public exploit identified at time of analysis. Vendor patches released April 2026 across all affected major branches.

Technical ContextAI

This vulnerability exploits Django's ASGI (Asynchronous Server Gateway Interface) request handling mechanism, specifically the HttpRequest.body attribute parser. Django implements DATA_UPLOAD_MAX_MEMORY_SIZE as a protection against excessive memory consumption from large POST requests. The flaw (CWE-770: Allocation of Resources Without Limits or Throttling) occurs when ASGI processes requests with missing or understated Content-Length headers-the framework fails to enforce memory limits during body parsing, allowing attackers to stream arbitrary amounts of data into server memory. This bypasses the intended quota enforcement that normally caps request body size. The vulnerability affects the Python-based Django web framework across three actively maintained release series (4.2.x LTS, 5.2.x, 6.0.x), with unsupported series like 5.0.x, 4.1.x, and 3.2.x potentially vulnerable but not officially evaluated. ASGI deployment contexts (using Daphne, Uvicorn, Hypercorn, or similar servers) are specifically at risk, while traditional WSGI deployments may not be affected.

RemediationAI

Upgrade immediately to patched Django releases: version 6.0.4 for the 6.0 series, version 5.2.13 for the 5.2 series, or version 4.2.30 for the 4.2 LTS series. Installation via pip with 'pip install Django==6.0.4' (or appropriate version for your branch) applies the fix. No workarounds exist that fully mitigate the issue-the vulnerability requires code-level corrections to ASGI request body parsing logic. Organizations using unsupported Django versions (5.0.x, 4.1.x, 3.2.x) should prioritize migration to a supported LTS branch (4.2.x) or current stable release. If immediate patching is impossible, consider temporary mitigations: deploy reverse proxies (nginx, HAProxy) with strict request size limits enforced at the HTTP layer, implement aggressive connection timeouts, or temporarily route traffic through WSGI rather than ASGI servers. Monitor memory utilization for abnormal spikes. Full remediation guidance and release notes at https://www.djangoproject.com/weblog/2026/apr/07/security-releases/ with security announcements via https://groups.google.com/g/django-announce.

More in Python

View all
CVE-2025-24016 CRITICAL POC
9.9 Feb 10

Wazuh SIEM platform versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI t

CVE-2025-27520 CRITICAL POC
9.8 Apr 04

BentoML version 1.4.2 and earlier contains an unauthenticated remote code execution vulnerability through insecure deser

CVE-2025-2945 CRITICAL POC
9.9 Apr 03

pgAdmin 4 contains critical remote code execution vulnerabilities in the Query Tool download and Cloud Deployment endpoi

CVE-2013-5093 MEDIUM POC
6.8 Sep 27

The renderLocalView function in render/views.py in graphite-web in Graphite 0.9.5 through 0.9.10 uses the pickle Python

CVE-2025-32375 CRITICAL POC
9.8 Apr 09

BentoML is a Python library for building online serving systems optimized for AI apps and model inference. Rated critica

CVE-2014-0224 HIGH POC
7.4 Jun 05

OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph

CVE-2024-21644 HIGH POC
7.5 Jan 08

pyLoad download manager version prior to 0.5.0b3.dev77 exposes the Flask SECRET_KEY through an unauthenticated endpoint.

CVE-2017-9462 HIGH POC
8.8 Jun 06

In Mercurial before 4.1.3, "hg serve --stdio" allows remote authenticated users to launch the Python debugger, and conse

CVE-2026-39987 CRITICAL POC
9.3 Apr 08

Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/

CVE-2024-21645 MEDIUM POC
5.3 Jan 08

pyLoad is the free and open-source Download Manager written in pure Python. Rated medium severity (CVSS 5.3), this vulne

CVE-2026-33017 CRITICAL POC
9.3 Mar 17

Langflow (a visual LLM pipeline builder) contains a critical unauthenticated code execution vulnerability (CVE-2026-3301

CVE-2026-55255 HIGH POC
8.4 Jun 19

Cross-user flow execution in Langflow (< 1.9.1) lets any authenticated API-key holder run another user's flow by passing

Vendor StatusVendor

SUSE

Severity: High
Product Status
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise Module for Package Hub 15 SP7 Fixed
openSUSE Leap 15.6 Fixed
SUSE Linux Enterprise Module for Package Hub 15 SP6 Fixed

Share

EUVD-2026-19648 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy