Changes between Version 41 and Version 42 of SecurityTeam

Timestamp:

Oct 22, 2026, 3:30:42 PM (2 days ago)

Author:

Jacob Walls

Comment:

Fix typo

SecurityTeam

@@ -260 +260 @@
 Django makes a deliberate choice not to harden against a compromised cache layer, for the same reason it does not harden against a compromised database layer: doing so is the operator's responsibility, and some underlying drivers use pickle internally in ways that would make blanket hardening impractical.
 
-If you're interested in optional signing as a defense-in-depth measure, that discussion is ongoing publicly [1] and has an solved ticket needing contribution [2].
+If you're interested in optional signing as a defense-in-depth measure, that discussion is ongoing publicly [1] and has an unresolved ticket needing contribution [2].
 
 Kind regards, the Django Security Team.