{"answers":{"affected":"1 open source package ship an affected version, including django. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-15337 in the wild and no public exploit code.","fix":"Upgrade django to a fixed version for your release line: 5.2.17 or 6.0.8.","what":"CVE-2026-15337 is a medium-severity denial of service vulnerability in Djangoproject Django, published on 4 Aug 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-15337 and fix it if it is affected.\n\nWhat it is: CVE-2026-15337 is a medium-severity denial of service vulnerability in Djangoproject Django, published on 4 Aug 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-15337 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django (Bitnami): affected all versions; fixed in 5.2.17, 6.0.8\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-15337/ (Markdown: https://insights.sbomify.com/CVE-2026-15337/index.md)","id":"CVE-2026-15337","markdown":"https://insights.sbomify.com/CVE-2026-15337/index.md","name":"CVE-2026-15337","record":{"aliases":["BIT-django-2026-15337","DEBIAN-CVE-2026-15337","GHSA-2f9m-qhxg-w5v5","MINI-9p5g-wh9h-2v9w","UBUNTU-CVE-2026-15337"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Django web framework","requires_auth":"none","summary":"Attackers can cause denial of service in Django by sending many long language codes to the set_language view, which is not routed by default.","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.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-789","name":"Memory Allocation with Excessive Size Value"}],"description":"An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8.\n`django.utils.translation.check_for_language()` is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory. Such codes reach the function through the `django.views.i18n.set_language()` view, which is not routed by default. The consumed memory is bounded, since request data is limited by the `DATA_UPLOAD_MAX_MEMORY_SIZE` setting (default 2.5 MB) and the cache holds a fixed maximum number of entries.\nEarlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected.\nDjango would like to thank Jaeyoung Jang for reporting this issue.","ecosystems":["Bitnami"],"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 check_for_language()","id":"CVE-2026-15337","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"djangoproject:django","products":["djangoproject:django"],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":7,"next":{"headline":"Path traversal in LA-Studio Element Kit for Elementor","id":"CVE-2026-15338"},"packages":[{"ecosystem":"Bitnami","fixed":["5.2.17","6.0.8"],"introduced":["0","6.0.0"],"last_affected":[],"package":"django","purl":"pkg:bitnami/django","source":"BIT-django-2026-15337"}],"prev":{"headline":"Missing authorization in Catch Themes Demo Import","id":"CVE-2026-15336"},"products":["Django"],"published":"2026-08-04","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":"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-08-04","vendors":["djangoproject"]},"summary":"Attackers can cause denial of service in Django by sending many long language codes to the set_language view, which is not routed by default.","url":"https://insights.sbomify.com/CVE-2026-15337/"}