Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 1.92% for the current model date.
BlackTreeCVE Intelligencedjangoproject · Django
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | py3-django | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 4.2.20-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | py3-django | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 4.2.20-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.21v3.21 · community | py3-django | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 4.2.20-r0 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Debian trixietrixie · source | python-django | Vendor fix publishedDebian records a fixed source-package version for this release. | 3:4.2.18-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | python-django | Vendor fix publishedDebian records a fixed source-package version for this release. | 3:3.2.25-0+deb12u1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | python-django | Vendor fix publishedDebian records a fixed source-package version for this release. | 3:4.2.18-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | python-django | Vendor fix publishedDebian records a fixed source-package version for this release. | 3:4.2.18-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | python-django | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 3:4.2.11-1ubuntu1.5 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| PyPIdjango | ECOSYSTEM: introduced 5.1; fixed 5.1.5 | 5.1.5 | OSV record ↗aggregator derived · 10 Sep 2026 |
| PyPIdjango | ECOSYSTEM: introduced 5.0; fixed 5.0.11 | 5.0.11 | OSV record ↗aggregator derived · 10 Sep 2026 |
| PyPIdjango | ECOSYSTEM: introduced 4.2; fixed 4.2.18 | 4.2.18 | OSV record ↗aggregator derived · 10 Sep 2026 |
| PyPIdjango | ECOSYSTEM: introduced 5.1; fixed 5.1.5 | 5.1.5 | OSV record ↗aggregator derived · 10 Sep 2026 |
| PyPIdjango | ECOSYSTEM: introduced 5.0; fixed 5.0.11 | 5.0.11 | OSV record ↗aggregator derived · 10 Sep 2026 |
| PyPIdjango | ECOSYSTEM: introduced 4.2; fixed 4.2.18 | 4.2.18 | OSV record ↗aggregator derived · 10 Sep 2026 |
| pipDjango | >= 5.1, < 5.1.5 | 5.1.5 | GitHub advisory ↗github reviewed aggregator · 20 May 2025 |
| pipDjango | >= 5.0, < 5.0.11 | 5.0.11 | GitHub advisory ↗github reviewed aggregator · 20 May 2025 |
| pipDjango | >= 4.2, < 4.2.18 | 4.2.18 | GitHub advisory ↗github reviewed aggregator · 20 May 2025 |
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products as affected by this CVE.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch availableAn issue was discovered in Django 5.1 before 5.1.5, 5.0 before 5.0.11, and 4.2 before 4.2.18. Lack of upper-bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack. The undocumented and private functions clean_ipv6_address and is_valid_ipv6_address are vulnerable, as is the django.forms.GenericIPAddressField form field. (The django.db.models.GenericIPAddressField model field is not affected.)
An issue was discovered in Django 5.1 before 5.1.5, 5.0 before 5.0.11, and 4.2 before 4.2.18. Lack of upper-bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack. The undocumented and private functions clean_ipv6_address and is_valid_ipv6_address are vulnerable, as is the django.forms.GenericIPAddressField form field. (The django.db.models.GenericIPAddressField model field is not affected.)
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
An issue was discovered in Django 5.1 before 5.1.5, 5.0 before 5.0.11, and 4.2 before 4.2.18. Lack of upper-bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack. The undocumented and private functions clean_ipv6_address and is_valid_ipv6_address are vulnerable, as is the django.forms.GenericIPAddressField form field. (The django.db.models.GenericIPAddressField model field is not affected.)
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-770: Allocation of Resources Without Limits or Throttling. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:LCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
Published 14 Jan 2025 · Last source change 12 Feb 2025, 20:31 UTC · CWE-770 · Allocation of Resources Without Limits or Throttling
Core structured fields are present and their contributing authorities are shown above.