CVE-2011-4136 · cross-distro fix matrix

CVE-2011-4136: django.contrib.sessions in Django before 1.2.7 and 1.3.x before 1.3.1, when session data is stored in the cache, uses the root namespace for both session identifiers and application-data keys, which allows remote attackers to modify a session by triggering use of a key that is equal to that session'

Affects 3 Linux releases across 3 (distro × package) combinations.

Fix per ecosystem

Each block below is a distro release where CVE-2011-4136 has a known fix. Run the listed command on that distro to remediate.

Debian bullseye

Source: Debian Security Tracker

python-django→ fixed in1.3.1-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y python-django
```

Debian bookworm

Source: Debian Security Tracker

python-django→ fixed in1.3.1-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y python-django
```

Debian trixie

Source: Debian Security Tracker

python-django→ fixed in1.3.1-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y python-django
```

Are YOU affected by CVE-2011-4136?

5-second check on your actual server. Reads /etc/os-release, uname -r, and the distro's package manager; matches against this same cross-source index live.

curl https://mindsparkstack.com/scan.sh | bash

Form-based quickscan View on NVD

Continuous monitoring beats manual checking

CVE-2011-4136dropped silently in your distro's update channel. Every new CVE is the same story. StackPatch runs the matcher hourly against all 5 sources and emails the exact remediation when something new applies to one of your servers. $99 lifetime, 50 founder seats, 30-day refund.

See StackPatch ($99 lifetime)