CVE-2022-24840: django-s3file is a lightweight file upload input for Django and Amazon S3

Q: How do I fix CVE-2022-24840?

django-s3file: upgrade to 5.5.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-24840 being exploited?

CVE-2022-24840 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-24840 affect?

CVE-2022-24840 affects django-s3file. Severity is critical (CVSS 9.1). django-s3file is a lightweight file upload input for Django and Amazon S3 . In versions prior to 5.5.1 it was possible to traverse the entire AWS S3 bucket and in most cases to access or delete files. If the `AWS_LOCATION` setting was set,

Q: How urgent is CVE-2022-24840?

Priority 67/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

This week

CRITICAL 9.1REMOTEWATCHLISTUPGRADE

CVE-2022-24840 is a critical-severity flaw (CVSS 9.1) affecting django-s3file. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

django-s3file is a lightweight file upload input for Django and Amazon S3 . In versions prior to 5.5.1 it was possible to traverse the entire AWS S3 bucket and in most cases to access or delete files. If the `AWS_LOCATION` setting was set, traversal was limited to that location only. The issue was discovered by the maintainer. There were no reports of the vulnerability being known to or exploited by a third party, prior to the release of the patc

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	9.1 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.1% (top 19%)
CISA exploited list	No
Weakness	CWE-22
Published	2022-06-09
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: django-s3file project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-06-09 04:15 UTCPublished CVE record published
2026-06-17 04:32 UTCUpdated Record last modified

django-s3file project django-s3file UPGRADE

Affected: < 5.5.1

Fixed in: 5.5.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy django-s3file || rpm -q django-s3file || django-s3file --version

2. UPGRADE to 5.5.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade django-s3file

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade django-s3file

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-24840?

django-s3file: upgrade to 5.5.1. Exact commands for each OS are on this page.

Is CVE-2022-24840 being exploited?

CVE-2022-24840 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-24840 affect?

CVE-2022-24840 affects django-s3file. Severity is critical (CVSS 9.1). django-s3file is a lightweight file upload input for Django and Amazon S3 . In versions prior to 5.5.1 it was possible to traverse the entire AWS S3 bucket and in most cases to access or delete files. If the `AWS_LOCATION` setting was set,

How urgent is CVE-2022-24840?

Priority 67/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Django vulnerabilities · AWS vulnerabilities

References

← Back to latest CVEs