{"answers":{"affected":"6 open source packages ship an affected version, including django. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-8404 in the wild and no public exploit code.","fix":"Upgrade django to a fixed version for your release line: 5.2.15 or 6.0.6.","what":"CVE-2026-8404 is a low-severity vulnerability in Djangoproject Django, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-8404 and fix it if it is affected.\n\nWhat it is: CVE-2026-8404 is a low-severity vulnerability in Djangoproject Django, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-8404 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.15, 6.0.6\n- django (PyPI): affected all versions; fixed in 5.2.15\n- django (PyPI): affected all versions; fixed in 5.2.15\n- django (PyPI): affected from 5.2; fixed in 5.2.15, 6.0.6\n- django (PyPI): affected from 6.0.0; fixed in 6.0.6\n- django (PyPI): affected from 6.0.0; fixed in 6.0.6\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-8404/ (Markdown: https://insights.sbomify.com/CVE-2026-8404/index.md)","id":"CVE-2026-8404","markdown":"https://insights.sbomify.com/CVE-2026-8404/index.md","name":"CVE-2026-8404","record":{"aliases":["BIT-django-2026-8404","DEBIAN-CVE-2026-8404","ECHO-a707-d13a-55ba","GHSA-8cjm-8mp7-r2xf","MINI-96q7-rxvv-qxrh","MINI-wgm2-q4p5-2jww","PYSEC-2026-201","UBUNTU-CVE-2026-8404"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Django web framework","requires_auth":"none","summary":"Attackers can read sensitive cached responses because Django's cache middleware fails to match Cache-Control directives case-insensitively.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"DSF","cpe":[{"product":"django","vendor":"djangoproject"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-178","name":"Improper Handling of Case Sensitivity"}],"description":"An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6.\n`django.middleware.cache.UpdateCacheMiddleware` in Django does not match `Cache-Control` response directives case-insensitively, which allows remote attackers to read responses that were incorrectly cached because their `Cache-Control` directives used uppercase or mixed-case values.\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 Ahmed Badawe 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 exposure of private data via case-sensitive Cache-Control directives in UpdateCacheMiddleware","id":"CVE-2026-8404","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"djangoproject:django","products":["djangoproject:django"],"type":"information_disclosure","year":"2026"},"n_packages":6,"n_references":3,"next":{"headline":"IBM Guardium Data Protection is affected by Exposure of Sensitive Information vulnerability","id":"CVE-2026-8405"},"packages":[{"ecosystem":"Bitnami","fixed":["5.2.15","6.0.6"],"introduced":["5.2.0","6.0.0"],"last_affected":[],"package":"django","purl":"pkg:bitnami/django","source":"BIT-django-2026-8404"},{"ecosystem":"PyPI","fixed":["5.2.15"],"introduced":["0"],"last_affected":[],"package":"django","purl":null,"source":"GHSA-8cjm-8mp7-r2xf"},{"ecosystem":"PyPI","fixed":["5.2.15"],"introduced":["0"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-8cjm-8mp7-r2xf"},{"ecosystem":"PyPI","fixed":["5.2.15","6.0.6"],"introduced":["5.2","6.0"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"PYSEC-2026-201"},{"ecosystem":"PyPI","fixed":["6.0.6"],"introduced":["6.0.0"],"last_affected":[],"package":"django","purl":null,"source":"GHSA-8cjm-8mp7-r2xf"},{"ecosystem":"PyPI","fixed":["6.0.6"],"introduced":["6.0.0"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-8cjm-8mp7-r2xf"}],"prev":{"headline":"Stored XSS in Exagate's SYSGUARD 6001","id":"CVE-2026-8403"},"products":["Django"],"published":"2026-06-03","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-06-03","vendors":["djangoproject"]},"summary":"Attackers can read sensitive cached responses because Django's cache middleware fails to match Cache-Control directives case-insensitively.","url":"https://insights.sbomify.com/CVE-2026-8404/"}