The vulnerability in Django's django.http.HttpRequest.get_signed_cookie arises from the use of a non-injective salt derivation approach, which concatenates the cookie name and salt argument. This design flaw enables a remote attacker to use a signed cookie in a context other than the one it was originally signed for by finding distinct (name, salt) pairs that yield the same concatenated value. The affected versions explicitly include Django 6.0 and 5.2, prior to versions 6.0.6 and 5.2.15 respectively. Earlier unsupported Django series such as 5.0.x, 4.1.x, and 3.2.x have not been evaluated but may also be vulnerable. The vulnerability is tracked as CWE-347 (Improper Verification of Cryptographic Signature).

The impact is limited to confidentiality as the vulnerability allows an attacker to reuse a signed cookie in an unintended context, potentially bypassing intended cookie validation boundaries. There is no indication of integrity or availability impact. The CVSS score of 3.1 reflects a low severity with network attack vector, high attack complexity, low privileges required, and no user interaction needed.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official patch or remediation level is provided, users should monitor djangoproject advisories for updates. Avoid relying on the affected versions (=6.0, =5.2) for sensitive cookie signing until a fix is released. No other specific mitigations are indicated by the vendor advisory.