Denial of service in django

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2011-4137: 3.02% estimated exploitation activity in the next 30 days; percentile 87.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The verifyexists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 relies on Python libraries that attempt access to an arbitrary URL with no timeout, which allows remote attackers to cause a denial of service (resource consumption) via a URL associated with (1) a slow response, (2) a completed TCP connection with no application data sent, or (3) a large amount of application data, a related issue to CVE-2011-1521.

Published by the source

23 Jul 2018, 19:51 UTC

Last modified by the source

16 Sep 2024, 22:45 UTC

Source last checked

26 Oct 2026, 13:17 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-3jqw-crqj-w8qw

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-3jqw-crqj-w8qw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2011-4137

Advisory: Denial of service in django
IDs: CVE-2011-4137, GHSA-3jqw-crqj-w8qw
Record: https://patchnext.com/advisories/cve-2011-4137 (revision 3, source checked 26 Oct 2026, 13:17 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: django 1.3.1, 1.2.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI django: affected < 1.2.7; >= 1.3, < 1.3.1; fixed in 1.3.1, 1.2.7

## Suggested inspection (read-only)
- `python -m pip show django`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on django.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3jqw-crqj-w8qw (OSV record GHSA-3jqw-crqj-w8qw lists affected ranges: PyPI django >=0 =1.3 <1.3.1 (fixed))
- Verified: https://github.com/advisories/GHSA-3jqw-crqj-w8qw (GitHub-reviewed advisory GHSA-3jqw-crqj-w8qw lists affected ranges: PyPI django >=0 =1.3 <1.3.1)

Commands are suggestions: review each one before running it.