Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Django versions 5.2 before 5.2.15 and 6.0 before 6.0.6 are vulnerable. Signed cookies can be used in a context other than the one where they were signed, because the salt derivation combines the cookie name and salt in a way that lets different pairs collide. The source does not describe what an attacker needs beyond being able to send requests, and it notes that earlier unsupported series were not evaluated. Upgrade to Django 5.2.15 or 6.0.6.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 2.3 | Low | 4.0 | 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 | CNA (DSF) |
- CISA KEV Not listed.
- EPSS 0.0024, the 15th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:29 UTC First seen by agentprime
- 31 Oct 2026, 14:29 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-h7pc-vwp9-298g
- OSV: GHSA-h7pc-vwp9-298g
- nvd.nist.gov/vuln/detail/CVE-2026-6873
- github.com/django/django/commit/594360cbf58be7f56eb6da96d58644297c99ef85
- github.com/django/django/commit/70d36515b9cc71700105a14b275583070d48b689
- github.com/django/django/commit/c807d9c398022d23cb27518fa6ecaf343efb30cf
- docs.djangoproject.com/en/dev/releases/security
- github.com/django/django
- github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2026-199.yaml
- groups.google.com/g/django-announce
- www.djangoproject.com/weblog/2026/jun/03/security-releases