Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

GHSA-vm8q-m57g-pff3 — django

MEDIUMFix: django/django@072963e

GHSA-vm8q-m57g-pff3 is a medium-severity (CVSS 5.3) CWE-1333 vulnerability in django. A fix is available for django — see the affected versions and patch details below.

Regular expression denial-of-service in Django

Also known asBIT-django-2024-27351CVE-2024-27351PYSEC-2024-47
Published
Mar 15, 2024
Updated
Sep 10, 2026
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Sep 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-vm8q-m57g-pff3.

EPSS Exploitation Probability

via FIRST.org ↗
1.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-vm8q-m57g-pff3 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

3 pkgs affected
🐍django🐍django🐍django

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

In Django 3.2 before 3.2.25, 4.2 before 4.2.11, and 5.0 before 5.0.3, the django.utils.text.Truncator.words() method (with html=True) and the truncatewords_html template filter are subject to a potential regular expression denial-of-service attack via a crafted string. NOTE: this issue exists because of an incomplete fix for CVE-2019-14232 and CVE-2023-43665.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIdjango≥ 3.2&&< 3.2.253.2.25pip install --upgrade 'django==3.2.25'
🐍PyPIdjango≥ 4.2&&< 4.2.114.2.11pip install --upgrade 'django==4.2.11'
🐍PyPIdjango≥ 5.0&&< 5.0.35.0.3pip install --upgrade 'django==5.0.3'

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update django to 3.2.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vm8q-m57g-pff3 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vm8q-m57g-pff3 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-vm8q-m57g-pff3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
Red Hat Ansible Automation Platform 2.4 for RHEL 8python3x-django-0:4.2.11-1.el8apRHSA-2024:1640
Red Hat Ansible Automation Platform 2.4 for RHEL 8automation-controller-0:4.5.7-1.el8apRHSA-2024:3781
Red Hat OpenStack Platform 17.1 for RHEL 9python-django-0:2.2.24-9.el9ostRHSA-2025:4187
Red Hat Satellite 6.15 for RHEL 8python-django-0:4.2.14-1.el8pcRHSA-2024:5662
RHUI 4 for RHEL 8python-django-0:4.2.11-1.el8uiRHSA-2024:1878

Frequently Asked Questions

In Django 3.2 before 3.2.25, 4.2 before 4.2.11, and 5.0 before 5.0.3, the django.utils.text.Truncator.words() method (with html=True) and the truncatewords_html template filter are subject to a potential regular expression denial-of-service attack via a crafted string. NOTE: this issue exists because of an incomplete fix for CVE-2019-14232 and CVE-2023-43665.
O3 Security · Impact-Aware SCA

Is GHSA-vm8q-m57g-pff3 in your dependencies?

O3 Security finds GHSA-vm8q-m57g-pff3 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-vm8q-m57g-pff3: django (Medium 5.3) | O3 Security