Advisory record · GHSA-4rrr-2h4v-f3j9

Django has Inefficient Algorithmic Complexity

CVSS 7.5 HighEPSS 0.011 · 66th percentile

Published by the GitHub Advisory Database at 3 Feb 2026, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
djangoPyPI>=6.0a1, <6.0.2 || >=5.2a1, <5.2.11 || >=4.2a1, <4.2.286.0.2, 5.2.11, 4.2.28
Identifiers
GHSA-4rrr-2h4v-f3j9 · BIT-django-2026-1285 · CVE-2026-1285 · PYSEC-2026-45
Weakness (CWE)
CWE-407
Published
3 Feb 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Django versions from 4.2 before 4.2.28, from 5.2 before 5.2.11, and from 6.0 before 6.0.2 are vulnerable. A remote attacker can supply crafted input containing many unmatched HTML end tags to the Truncator chars() and words() methods (with html=True) or the truncatechars_html and truncatewords_html template filters, causing a denial of service. Upgrade to Django 4.2.28, 5.2.11, or 6.0.2. Earlier unsupported series may also be affected and were not evaluated.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H ADP (CISA-ADP)
  • CISA KEV Not listed.
  • EPSS 0.011, the 66th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:34 UTC First seen by agentprime
  2. 31 Oct 2026, 14:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.