CVE-2026-1285: Potential denial-of-service vulnerability in django.utils.text.Truncator HTML methods
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 66.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: djangoproject Django 4.2.28, 5.2.11, 6.0.2.
Low priority for now. Upgrade to djangoproject Django 4.2.28, 5.2.11, 6.0.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28. `django.utils.text.Truncator.chars()` and `Truncator.words()` methods (with `html=True`) and the `truncatechars_html` and `truncatewords_html` template filters allow a remote attacker to cause a potential denial-of-service via crafted inputs containing a large number of unmatched HTML end tags. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Seokchan Yoon for reporting this issue.
- Published
- Feb 3, 2026
- Updated
- Jun 17, 2026
- EPSS
- 1.1% · 66th percentile
- CWE
- CWE-407
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| djangoproject | django | cpe:2.3:a:djangoproject:django |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- djangoproject django4.2 and later · before 4.2.28
- djangoproject django5.2 and later · before 5.2.11
- djangoproject django6.0 and later · before 6.0.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (DSF). Independent of NVD's CPE analysis and usually ahead of it.
djangoproject Django
- 6.0.2, 5.2.11, 4.2.28not affected
- 6.0 and later · before 6.0.2affected · semver
- 5.2 and later · before 5.2.11affected · semver
- 4.2 and later · before 4.2.28affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | python-django | before 2:2.2.28-1~deb11u12 | 2:2.2.28-1~deb11u12 |
| Debian:12 | python-django | before 3:3.2.25-0+deb12u2 | 3:3.2.25-0+deb12u2 |
| Debian:13 | python-django | before 3:4.2.28-0+deb13u1 | 3:4.2.28-0+deb13u1 |
| Debian:14 | python-django | before 3:4.2.28-1 | 3:4.2.28-1 |
| openSUSE:Leap 15.6 | python-Django | before 4.2.11-150600.3.47.1 | 4.2.11-150600.3.47.1 |
| openSUSE:Leap 16.0 | python-Django | before 5.2.4-bp160.5.1 | 5.2.4-bp160.5.1 |
| openSUSE:Tumbleweed | python-Django | before 5.2.11-1.1 | 5.2.11-1.1 |
| openSUSE:Tumbleweed | python-Django4 | before 4.2.28-1.1 | 4.2.28-1.1 |
| openSUSE:Tumbleweed | python-Django6 | before 6.0.2-1.1 | 6.0.2-1.1 |
| PyPI | django | from 4.2 · before 4.2.28 | 4.2.28 |
| PyPI | django | from 4.2a1 · before 4.2.28 | 4.2.28 |
| PyPI | django | from 5.2 · before 5.2.11 | 5.2.11 |
| PyPI | django | from 5.2a1 · before 5.2.11 | 5.2.11 |
| PyPI | django | from 6.0 · before 6.0.2 | 6.0.2 |
| PyPI | django | from 6.0a1 · before 6.0.2 | 6.0.2 |
| Red Hat:ansible_automation_platform_developer:2.5::el8 | automation-controller | before 0:4.6.26-1.el8ap | 0:4.6.26-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.5::el8 | automation-controller-cli | before 0:4.6.26-1.el8ap | 0:4.6.26-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.5::el8 | python3.12-django | before 0:4.2.28-1.el8ap | 0:4.2.28-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.5::el8 | receptor | before 0:1.6.3-4.el8ap | 0:1.6.3-4.el8ap |
| Red Hat:ansible_automation_platform_developer:2.5::el8 | receptorctl | before 0:1.6.3-4.el8ap | 0:1.6.3-4.el8ap |
| Red Hat:ansible_automation_platform_developer:2.5::el9 | automation-controller | before 0:4.6.26-1.el9ap | 0:4.6.26-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.5::el9 | automation-controller-cli | before 0:4.6.26-1.el9ap | 0:4.6.26-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.6::el9 | automation-controller | before 0:4.7.9-1.el9ap | 0:4.7.9-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.6::el9 | automation-controller-cli | before 0:4.7.9-1.el9ap | 0:4.7.9-1.el9ap |
+96
Same product
djangoproject: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-34265An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.61This week
- CVE-2020-7471Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter 59Plan
- CVE-2019-19844Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover.55Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-14550Feb 3, 2026 · Potential denial-of-service vulnerability via repeated headers when using ASGI30Monitor
- ← EarlierCVE-2026-1207Feb 3, 2026 · Potential SQL injection via raster lookups on PostGIS25Monitor
- Later →CVE-2026-1287Feb 3, 2026 · Potential SQL injection in column aliases via control characters21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| djangoproject Django | 4.2.28 | Vendor (CNA) |
| djangoproject Django | 5.2.11 | Vendor (CNA) |
| djangoproject Django | 6.0.2 | Vendor (CNA) |
| debian:python-django | 3:3.2.25-0+deb12u2 · Debian:12 | Package registry (OSV) |
| opensuse:python-Django | 4.2.11-150600.3.47.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:python-Django4 | 4.2.28-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:python-Django6 | 6.0.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:django | 4.2.28 | Package registry (OSV) |
| PyPI:django | 5.2.11 | Package registry (OSV) |
| PyPI:django | 6.0.2 | Package registry (OSV) |
| red hat:automation-platform-ui | 0:2.6.6-1.el9ap · Red Hat:ansible_automation_platform:2.6::el9 | Package registry (OSV) |
| red hat:python3.12-aiohttp | 0:3.13.3-2.el9ap · Red Hat:ansible_automation_platform:2.6::el9 | Package registry (OSV) |
| red hat:python3.12-aiohttp-debuginfo | 0:3.13.3-2.el9ap · Red Hat:ansible_automation_platform:2.6::el9 | Package registry (OSV) |
| red hat:python3.12-aiohttp-debugsource | 0:3.13.3-2.el9ap · Red Hat:ansible_automation_platform:2.6::el9 | Package registry (OSV) |
| red hat:python3.12-django | 0:4.2.30-1.el9pc · Red Hat:satellite_capsule:6.18::el9 | Package registry (OSV) |
| red hat:python3.12-markdown | 0:3.8.2-1.el9pc · Red Hat:satellite_capsule:6.18::el9 | Package registry (OSV) |
| red hat:python3.12-pyOpenSSL | 0:26.0.0-2.el9pc · Red Hat:satellite_capsule:6.18::el9 | Package registry (OSV) |
| red hat:receptor | 0:1.6.3-4.el10ap · Red Hat:ansible_automation_platform:2.6::el10 | Package registry (OSV) |
| red hat:receptor-debuginfo | 0:1.6.3-4.el10ap · Red Hat:ansible_automation_platform:2.6::el10 | Package registry (OSV) |
| red hat:receptor-debugsource | 0:1.6.3-4.el10ap · Red Hat:ansible_automation_platform:2.6::el10 | Package registry (OSV) |
| red hat:receptorctl | 0:1.6.3-4.el10ap · Red Hat:ansible_automation_platform:2.6::el10 | Package registry (OSV) |
| red hat:rubygem-activesupport | 0:7.0.8.7-2.el9sat · Red Hat:satellite_capsule:6.18::el9 | Package registry (OSV) |
| suse:python-Django | 4.2.11-150600.3.47.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Seokchan Yoonreporter
- Natalia Bidartremediation developer
- Jacob Wallscoordinator
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-6446063 days apartPotential denial-of-service vulnerability in XML serializer text extraction31Monitor
- CVE-2025-6445890 days apartPotential denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows31Monitor
- CVE-2025-145500 days apartPotential denial-of-service vulnerability via repeated headers when using ASGI30Monitor
- CVE-2026-84429245 days apartPotential denial-of-service vulnerability in HTTP header parsing27Monitor
- CVE-2026-3303363 days apartPotential denial-of-service vulnerability in MultiPartParser via base64-encoded file upload26Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-407 · Inefficient Algorithmic ComplexityCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.