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

CVE-2021-44420 — django

HIGHFix: django/django@d4dcd5b

CVE-2021-44420 is a high-severity (CVSS 7.3) vulnerability in django. A fix is available for django — see the affected versions and patch details below.

Potential bypass of an upstream access control based on URL paths in Django

Also known asBIT-django-2021-44420GHSA-v6rh-hp5x-86rvPYSEC-2021-439
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk
0.00%1.07%2.13%3.20%0.1%2.5%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-44420 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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 2.2 before 2.2.25, 3.1 before 3.1.14, and 3.2 before 3.2.10, HTTP requests for URLs with trailing newlines could bypass upstream access control based on URL paths. This issue has low severity, according to the Django security policy.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIdjango≥ 2.2a1&&< 2.2.252.2.25pip install --upgrade 'django==2.2.25'
🐍PyPIdjango≥ 3.0a1&&< 3.1.143.1.14pip install --upgrade 'django==3.1.14'
🐍PyPIdjango≥ 3.2a1&&< 3.2.103.2.10pip install --upgrade 'django==3.2.10'

Affected Products

5 products · 10 configurations
OS
ubuntu linuxcanonical
3 versions
20.0421.0421.10
OS
debian linuxdebian
2 versions
10.011.0
Application
djangodjangoproject
≥ 3.2 && < 3.2.10
range
OS
fedorafedoraproject
1 version
35
OS
satelliteredhat
1 version
6.0

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 2.2.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-44420 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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 HatLow
ProductFixed inAdvisory
Red Hat Satellite 6.11 for RHEL 8python-django-0:3.2.13-1.el8pcRHSA-2022:5498
RHUI 4 for RHEL 8python-django-0:3.2.16-1.0.1.el8uiRHSA-2023:0742

Frequently Asked Questions

In Django 2.2 before 2.2.25, 3.1 before 3.1.14, and 3.2 before 3.2.10, HTTP requests for URLs with trailing newlines could bypass upstream access control based on URL paths. This issue has low severity, according to the Django security policy.
O3 Security · Impact-Aware SCA

Is CVE-2021-44420 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2021-44420: django — Fixed in 2.2.25