{"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-6873 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-6873 is a low-severity vulnerability in Djangoproject Django, published on 3 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-6873 and fix it if it is affected.\n\nWhat it is: CVE-2026-6873 is a low-severity vulnerability in Djangoproject Django, published on 3 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-6873 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-6873/ (Markdown: https://insights.sbomify.com/CVE-2026-6873/index.md)","id":"CVE-2026-6873","markdown":"https://insights.sbomify.com/CVE-2026-6873/index.md","name":"CVE-2026-6873","record":{"aliases":["BIT-django-2026-6873","DEBIAN-CVE-2026-6873","ECHO-24f0-9b34-d0ae","GHSA-h7pc-vwp9-298g","MINI-83v4-8hhc-2939","MINI-wgjg-pmvc-m9mc","PYSEC-2026-199","UBUNTU-CVE-2026-6873"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Django web framework","requires_auth":"low_privilege","summary":"Attackers can bypass signed cookie validation by exploiting salt namespace collisions, allowing cookie reuse across different contexts.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"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:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15.\n`django.http.HttpRequest.get_signed_cookie` in Django uses a non-injective salt derivation (concatenating the cookie name and salt argument), which allows a remote attacker to use a cookie in a context different from the one where it was signed, via distinct `(name, salt)` pairs that produce the same concatenation.\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 Peng Zhou 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":"Signed cookie salt namespace collision in django.http.HttpRequest.get_signed_cookie","id":"CVE-2026-6873","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"djangoproject:django","products":["djangoproject:django"],"type":"security_feature_bypass","year":"2026"},"n_packages":6,"n_references":3,"next":{"headline":"ericc-ch copilot-api Header token dns rebinding","id":"CVE-2026-6874"},"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-6873"},{"ecosystem":"PyPI","fixed":["5.2.15"],"introduced":["0"],"last_affected":[],"package":"django","purl":null,"source":"GHSA-h7pc-vwp9-298g"},{"ecosystem":"PyPI","fixed":["5.2.15"],"introduced":["0"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-h7pc-vwp9-298g"},{"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-199"},{"ecosystem":"PyPI","fixed":["6.0.6"],"introduced":["6.0.0"],"last_affected":[],"package":"django","purl":null,"source":"GHSA-h7pc-vwp9-298g"},{"ecosystem":"PyPI","fixed":["6.0.6"],"introduced":["6.0.0"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-h7pc-vwp9-298g"}],"prev":{"headline":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2026-6872"},"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 bypass signed cookie validation by exploiting salt namespace collisions, allowing cookie reuse across different contexts.","url":"https://insights.sbomify.com/CVE-2026-6873/"}