CVE-2009-3695 · cross-distro fix matrix

CVE-2009-3695: Algorithmic complexity vulnerability in the forms library in Django 1.0 before 1.0.4 and 1.1 before 1.1.1 allows remote attackers to cause a denial of service (CPU consumption) via a crafted (1) EmailField (email address) or (2) URLField (URL) that triggers a large amount of backtracking in a regula

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

Fix per ecosystem

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

Debian bullseye

Source: Debian Security Tracker

python-django→ fixed in1.1.1-1urgency: medium

sudo apt-get install --only-upgrade -y python-django

Debian bookworm

Source: Debian Security Tracker

python-django→ fixed in1.1.1-1urgency: medium

sudo apt-get install --only-upgrade -y python-django

Debian trixie

Source: Debian Security Tracker

python-django→ fixed in1.1.1-1urgency: medium

sudo apt-get install --only-upgrade -y python-django

Are YOU affected by CVE-2009-3695?

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-2009-3695dropped 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)