CVE-2026-6873: Signed cookie salt namespace collision in django.http.HttpRequest.get_signed_cookie

Published Jun 3, 2026
·
Updated

An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15. django.http.HttpRequest.getsignedcookie 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. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Peng Zhou for reporting this issue.

Affected Software

3 affected components
pypi/django<6.0.6, <5.2.15
djangoproject Django>=5.2<5.2.15
djangoproject Django>=6.0<6.0.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 6.0.6
  2. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 5.2.15

Event History

Jun 3, 2026
CVE Published
via MITRE·01:16 PM
Data Sourced
via MITRE·01:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-6873?

The severity of CVE-2026-6873 is classified as low with a score of 2.3.

2

How do I fix CVE-2026-6873?

To fix CVE-2026-6873, upgrade to Django versions 6.0.6 or 5.2.15 or later.

3

What systems are affected by CVE-2026-6873?

CVE-2026-6873 affects Django versions prior to 6.0.6 and 5.2.15.

4

What is the impact of CVE-2026-6873?

CVE-2026-6873 allows a remote attacker to potentially use a signed cookie in an inappropriate context.

5

Is there a workaround for CVE-2026-6873?

There are no specific workarounds; upgrading Django is the recommended solution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203