{"answers":{"affected":"6 open source packages ship an affected version, including django and Django. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-5766 in the wild and no public exploit code.","fix":"Upgrade django to a fixed version for your release line: 5.2.14 or 6.0.5.","what":"CVE-2026-5766 is a medium-severity denial of service vulnerability in Djangoproject Django, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-5766 and fix it if it is affected.\n\nWhat it is: CVE-2026-5766 is a medium-severity denial of service vulnerability in Djangoproject Django, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-5766 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django (Bitnami): affected from 5.2.0; fixed in 5.2.14, 6.0.5\n- django (PyPI): affected from 5.2; fixed in 5.2.14, 6.0.5\n- django (PyPI): affected from 5.2; fixed in 5.2.14\n- django (PyPI): affected from 6.0; fixed in 6.0.5\n- Django (PyPI): affected from 5.2; fixed in 5.2.14\n- Django (PyPI): affected from 6.0; fixed in 6.0.5\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-5766/ (Markdown: https://insights.sbomify.com/CVE-2026-5766/index.md)","id":"CVE-2026-5766","markdown":"https://insights.sbomify.com/CVE-2026-5766/index.md","name":"CVE-2026-5766","record":{"aliases":["BIT-django-2026-5766","DEBIAN-CVE-2026-5766","ECHO-35cc-781b-4acf","GHSA-w26r-rmm8-9c29","MINI-fgm7-pq75-6c3m","PYSEC-2026-54"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Django web framework","requires_auth":"none","summary":"Attackers can cause denial of service in Django ASGI applications by bypassing file upload memory limits via manipulated Content-Length headers.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"DSF","cpe":[{"product":"django","vendor":"djangoproject"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-130","name":"Improper Handling of Length Parameter Inconsistency"}],"description":"An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14.\nASGI requests with a missing or understated `Content-Length` header can bypass the `FILE_UPLOAD_MAX_MEMORY_SIZE` limit, potentially loading large files into memory and causing service degradation.\r\n \r\nAs a reminder, Django expects a limit to be configured at the web server level rather than solely relying on `FILE_UPLOAD_MAX_MEMORY_SIZE`.\nEarlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.\nDjango would like to thank Kyle Agronick for reporting this issue.","ecosystems":["Bitnami","PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Potential denial-of-service vulnerability in ASGI requests via file upload limit bypass","id":"CVE-2026-5766","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"djangoproject:django","products":["djangoproject:django"],"type":"denial_of_service","year":"2026"},"n_packages":6,"n_references":3,"next":{"headline":"SlideShowPro SC \u003c= 1.0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'album' Shortcode Attribute","id":"CVE-2026-5767"},"packages":[{"ecosystem":"Bitnami","fixed":["5.2.14","6.0.5"],"introduced":["5.2.0","6.0.0"],"last_affected":[],"package":"django","purl":"pkg:bitnami/django","source":"BIT-django-2026-5766"},{"ecosystem":"PyPI","fixed":["5.2.14"],"introduced":["5.2"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-w26r-rmm8-9c29"},{"ecosystem":"PyPI","fixed":["6.0.5"],"introduced":["6.0"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-w26r-rmm8-9c29"},{"ecosystem":"PyPI","fixed":["5.2.14","6.0.5"],"introduced":["5.2","6.0"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"PYSEC-2026-54"},{"ecosystem":"PyPI","fixed":["5.2.14"],"introduced":["5.2"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-w26r-rmm8-9c29"},{"ecosystem":"PyPI","fixed":["6.0.5"],"introduced":["6.0"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-w26r-rmm8-9c29"}],"prev":{"headline":"ReportIncident DiscussionTools integration causes slow requests","id":"CVE-2026-5762"},"products":["Django"],"published":"2026-05-05","related":[{"cvss_score":9.8,"headline":"Privilege abuse in GenericInlineModelAdmin","id":"CVE-2026-4277","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":9.8,"headline":"Django SQL injection in HasKey(lhs, rhs) on Oracle","id":"CVE-2024-53908","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":9.8,"headline":"Django SQL injection vulnerability","id":"CVE-2024-42005","kev_date_added":null,"published":"2024-08-07"},{"cvss_score":9.8,"headline":"Django bypasses validation when using one form field to upload multiple files","id":"CVE-2023-31047","kev_date_added":null,"published":"2023-05-07"},{"cvss_score":9.8,"headline":"Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection","id":"CVE-2022-34265","kev_date_added":null,"published":"2022-07-04"},{"cvss_score":9.8,"headline":"SQL Injection in Django","id":"CVE-2021-35042","kev_date_added":null,"published":"2021-07-02"},{"cvss_score":9.8,"headline":"SQL injection in Django","id":"CVE-2020-7471","kev_date_added":null,"published":"2020-02-03"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-06","vendors":["djangoproject"]},"summary":"Attackers can cause denial of service in Django ASGI applications by bypassing file upload memory limits via manipulated Content-Length headers.","url":"https://insights.sbomify.com/CVE-2026-5766/"}