Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2021-44420: 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 a

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: 2.4% (FIRST EPSS); higher than 84.1% 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.
  • Fixed version: py3-django (Alpine:v3.16) 3.2.12-r0; python-django (Debian:12) 2:3.2.10-1; python-Django (openSUSE:Leap 15.3) 2.2.28-bp153.2.3.1.

Low priority for now. Upgrade to py3-django (Alpine:v3.16) 3.2.12-r0; python-django (Debian:12) 2:3.2.10-1; python-Django (openSUSE:Leap 15.3) 2.2.28-bp153.2.3.1 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

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.

HighCVSS 7.3 · v3.1—No exploit Fix available
Published
Dec 7, 2021
Updated
Jun 17, 2026
EPSS
2.4% · 84th percentile
CWE
—

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
29 / 40 · 7.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.4%

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.

Follow CVE-2021-44420

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for djangoproject records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
djangoprojectdjango
redhatsatellite
debiandebian linux
canonicalubuntu linux
fedoraprojectfedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • canonical ubuntu linux20.04
  • canonical ubuntu linux21.04
  • canonical ubuntu linux21.10
  • debian debian linux10.0
  • debian debian linux11.0
  • djangoproject django2.2 and later · before 2.2.25
  • djangoproject django3.1 and later · before 3.1.14
  • djangoproject django3.2 and later · before 3.2.10
  • fedoraproject fedora35
  • redhat satellite6.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.16py3-djangobefore 3.2.12-r03.2.12-r0
Debian:12python-djangobefore 2:3.2.10-12:3.2.10-1
openSUSE:Leap 15.3python-Djangobefore 2.2.28-bp153.2.3.12.2.28-bp153.2.3.1
openSUSE:Tumbleweedpython-sentry-sdkbefore 2.20.0-1.12.20.0-1.1
openSUSE:Tumbleweedpython-sentry-sdkbefore 1.5.4-1.11.5.4-1.1
PyPIdjangofrom 2.2 · before 2.2.252.2.25
PyPIdjangofrom 2.2a1 · before 2.2.252.2.25
PyPIdjangofrom 3.0a1 · before 3.1.143.1.14
PyPIdjangofrom 3.1 · before 3.1.143.1.14
PyPIdjangofrom 3.2 · before 3.2.103.2.10
PyPIdjangofrom 3.2a1 · before 3.2.103.2.10
Red Hat:rhui:4::el8python-djangobefore 0:3.2.16-1.0.1.el8ui0:3.2.16-1.0.1.el8ui
Red Hat:rhui:4::el8python39-djangobefore 0:3.2.16-1.0.1.el8ui0:3.2.16-1.0.1.el8ui
Red Hat:satellite_capsule:6.11::el7foremanbefore 0:3.1.1.21-2.el7sat0:3.1.1.21-2.el7sat
Red Hat:satellite_capsule:6.11::el7libsolvbefore 0:0.7.22-1.el7pc0:0.7.22-1.el7pc
Red Hat:satellite_capsule:6.11::el7satellitebefore 0:6.11.0-2.el7sat0:6.11.0-2.el7sat
Red Hat:satellite_capsule:6.11::el8foremanbefore 0:3.1.1.21-2.el8sat0:3.1.1.21-2.el8sat
Red Hat:satellite_capsule:6.11::el8libsolvbefore 0:0.7.22-1.el8pc0:0.7.22-1.el8pc
Red Hat:satellite_capsule:6.11::el8python-djangobefore 0:3.2.13-1.el8pc0:3.2.13-1.el8pc
Red Hat:satellite_capsule:6.11::el8python-lxmlbefore 0:4.7.1-1.el8pc0:4.7.1-1.el8pc
Red Hat:satellite_capsule:6.11::el8python-sqlparsebefore 0:0.4.2-2.el8pc0:0.4.2-2.el8pc
Red Hat:satellite_capsule:6.11::el8python38-djangobefore 0:3.2.13-1.el8pc0:3.2.13-1.el8pc
Red Hat:satellite_capsule:6.11::el8satellitebefore 0:6.11.0-2.el8sat0:6.11.0-2.el8sat
Red Hat:satellite:6.11::el7candlepinbefore 0:4.1.13-1.el7sat0:4.1.13-1.el7sat

+12

Same product

djangoproject: all records

Other 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-2021-33571Jun 8, 2021 · In Django 2.2 before 2.2.24, 3.x before 3.1.12, and 3.2 before 3.2.4, URLValidator, validate_ipv4_address, and validate_ipv46_address do not
    32Monitor
  • ← EarlierCVE-2021-35042Jul 2, 2021 · Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a w
    52Plan
  • Later →CVE-2021-45115Jan 4, 2022 · An issue was discovered in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1.
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:py3-django3.2.12-r0 · Alpine:v3.16Package registry (OSV)
debian:python-django2:3.2.10-1 · Debian:12Package registry (OSV)
opensuse:python-Django2.2.28-bp153.2.3.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:python-sentry-sdk1.5.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
PyPI:django2.2.25Package registry (OSV)
PyPI:django3.1.14Package registry (OSV)
PyPI:django3.2.10Package registry (OSV)
red hat:candlepin0:4.1.13-1.el7sat · Red Hat:satellite:6.11::el7Package registry (OSV)
red hat:foreman0:3.1.1.21-2.el7sat · Red Hat:satellite_capsule:6.11::el7Package registry (OSV)
red hat:libsolv0:0.7.22-1.el7pc · Red Hat:satellite_capsule:6.11::el7Package registry (OSV)
red hat:python-django0:3.2.13-1.el8pc · Red Hat:satellite_capsule:6.11::el8Package registry (OSV)
red hat:python-lxml0:4.7.1-1.el8pc · Red Hat:satellite_capsule:6.11::el8Package registry (OSV)
red hat:python-sqlparse0:0.4.2-2.el8pc · Red Hat:satellite_capsule:6.11::el8Package registry (OSV)
red hat:python38-django0:3.2.13-1.el8pc · Red Hat:satellite_capsule:6.11::el8Package registry (OSV)
red hat:rubygem-puma0:5.6.2-1.el8sat · Red Hat:satellite:6.11::el8Package registry (OSV)
red hat:satellite0:6.11.0-2.el7sat · Red Hat:satellite_capsule:6.11::el7Package registry (OSV)
red hat:tfm-rubygem-actionpack0:6.0.4.7-1.el7sat · Red Hat:satellite:6.11::el7Package registry (OSV)
red hat:tfm-rubygem-puma0:5.6.2-1.el7sat · Red Hat:satellite:6.11::el7Package registry (OSV)
red hat:tfm-rubygem-sidekiq0:5.2.10-1.el7sat · Red Hat:satellite:6.11::el7Package registry (OSV)
rocky linux:libdb0:5.3.28-42.el8_4 · Rocky Linux:8Package registry (OSV)
suse:python-Django2.2.28-bp153.2.3.1 · SUSE:Package Hub 15 SP3Package 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.

No history yet (it accumulates with the daily EPSS job).

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 researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

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
low · data can be read
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
Low

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

nvd-primary

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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records