Skip to content
Fencer Vulns
medium 5.9

CVE-2007-5712 json

Django vulnerable to Denial of Service via i18n middleware component

published 2007-10-30 19 y ago modified 2026-06-16 4 mo ago also GHSA-9v8h-57gv-qch6 , PYSEC-2007-1 , EUVD-2007-0001

cvss
5.9
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

The internationalization (i18n) framework in Django 0.91, 0.95, 0.95.1, and 0.96, and as used in other products such as PyLucid, when the USE_I18N option and the i18n component are enabled, allows remote attackers to cause a denial of service (memory consumption) via many HTTP requests with large Accept-Language headers.

Patch / fix

  • pypi django 0.91.1, 0.95.2, 0.96.1, 1.1
  • python-django Debian 14, Debian 13, Debian 12 0.96-1.1

debian advisories DEBIAN-CVE-2007-5712

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2007-5712 updated

Django 0.96 i18n DoS

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.80% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 2.6 AV:N/AC:H/Au:N/C:N/I:N/A:P
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi django
>=0.96.0, <0.96.1
>=0.95, <0.95.2
>=0.91.0, <0.91.1
<1.1
0.96.1
0.95.2
0.91.1
1.1

Classification

Weakness
  • CWE-399 Resource Management Errors
  • CWE-400 Uncontrolled Resource Consumption
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.