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

CVE-2020-24584 — django

HIGHFix: django/django@1853724

CVE-2020-24584 is a high-severity (CVSS 7.5) Incorrect Default Permissions vulnerability in django. A fix is available for django — see the affected versions and patch details below.

Django Incorrect Default Permissions

Also known asBIT-django-2020-24584GHSA-fr28-569j-53c4PYSEC-2020-34
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
3.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk
2.25%2.77%3.28%3.80%3.3%3.3%Apr 26Jul 26Oct 26

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

How urgent is this, really

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

Where this sits among everything scored

Of 385,738 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

An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). The intermediate-level directories of the filesystem cache had the system's standard umask rather than 0o077.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIdjango≥ 2.2&&< 2.2.162.2.16pip install --upgrade 'django==2.2.16'
🐍PyPIdjango≥ 3.0&&< 3.0.103.0.10pip install --upgrade 'django==3.0.10'
🐍PyPIdjango≥ 3.1&&< 3.1.13.1.1pip install --upgrade 'django==3.1.1'

Affected Products

4 products · 8 configurations
OS
ubuntu linuxcanonical
1 version
20.04
Application
djangodjangoproject
≥ 3.1 && < 3.1.1
range
OS
fedorafedoraproject
3 versions
313233
Application
zfs storage appliance kitoracle
1 version
8.8

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

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). The intermediate-level directories of the filesystem cache had the system's standard umask rather than 0o077.
O3 Security · Impact-Aware SCA

Is CVE-2020-24584 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2020-24584: django — Fixed in 2.2.16