VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

django-s3file: vulnerability history, versions and safety

django-s3file is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 88 releases, from Jun 2022 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C2 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 29 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all django-s3file vulnerabilities

Vulert verdict on django-s3file 7.2.0 i

Updated on 23 Oct 2026

Action needed: 7.2.0 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 64/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 7.2.0 — affected i
  • Vulnerabilities on record 4 over 4 years · 2 in the last year i
  • Latest disclosure 29 Jun 2026 i
  • Highest CVSS 9.9 i
  • With no published fix 0 i
  • Stars 94 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for django-s3file, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
7.2.0 10 Oct 2026 U1 MIT Yes Details →
7.1.0 10 Oct 2026 U1 MIT Yes Details →
7.0.3 03 Jun 2026 U1 MIT Yes Details →
7.0.2 28 Apr 2026 U1 MIT Yes Details →
7.0.1 06 Jan 2026 C1 U1 MIT Yes Details →
7.0.0 06 Jan 2026 C1 U1 MIT Yes Details →
6.0.1 18 Dec 2025 C1 U1 MIT Yes Details →
5.5.7 06 Mar 2024 C1 U1 MIT Yes Details →
5.5.5 11 Dec 2023 C1 U1 MIT Yes Details →
5.5.4 06 Jun 2023 C1 U1 MIT Yes Details →
5.5.3 31 Mar 2023 C1 U1 MIT Yes Details →
5.5.2 30 Aug 2022 C1 U1 MIT Yes Details →
5.5.1 06 Jun 2022 C1 U1 MIT Yes Details →
5.5.0 19 Mar 2022 C2 U2 MIT Yes Details →
5.4.0 08 Sep 2021 C2 U2 MIT Yes Details →
5.3.0 02 Jun 2021 C2 U2 MIT Yes Details →
5.2.0 26 Oct 2020 C2 U2 MIT Yes Details →
5.1.3 22 Oct 2020 C2 U2 MIT Yes Details →
5.1.2 22 Oct 2020 C2 U2 MIT Yes Details →
5.1.1 20 Sep 2020 C2 U2 MIT Yes Details →
5.1.0 02 Sep 2020 C2 U2 MIT Yes Details →
5.0.6 15 Jul 2020 C2 U2 MIT Yes Details →
5.0.5 05 Jul 2019 C2 U2 MIT Yes Details →
5.0.4 04 Jul 2019 C2 U2 MIT Yes Details →
5.0.2 03 Jul 2019 C2 U2 MIT Yes Details →
5.0.1 03 Jul 2019 C2 U2 MIT Yes Details →
5.0.0 03 Jul 2019 C2 U2 MIT Yes Details →
4.2.0 27 Feb 2019 C2 U2 MIT Yes Details →
4.1.0 01 Nov 2018 C2 U2 MIT Yes Details →
4.0.2 12 Mar 2018 C2 U2 MIT Yes Details →
4.0.1 10 Mar 2018 C2 U2 MIT Yes Details →
4.0.0 10 Mar 2018 C2 U2 MIT Yes Details →
3.0.5 13 Nov 2017 C2 U2 MIT Yes Details →
3.0.4 13 Nov 2017 C2 U2 MIT Yes Details →
3.0.3 11 Nov 2017 C2 U2 MIT Yes Details →
3.0.2 13 Sep 2017 C2 U2 MIT Yes Details →
3.0.1 12 Sep 2017 C2 U2 MIT Yes Details →
3.0.0 09 Sep 2017 C2 U2 MIT Yes Details →
2.0.0 08 Sep 2017 C2 U2 MIT Yes Details →
1.2.1 29 Dec 2016 C2 U2 MIT Yes Details →
1.2.0 02 Feb 2016 C2 U2 MIT Yes Details →
1.1.0 11 Sep 2015 C2 U2 MIT Yes Details →
1.0.2 08 Sep 2015 C2 U2 MIT Yes Details →
1.0.1 07 Sep 2015 C2 U2 MIT Yes Details →
1.0.0 05 Sep 2015 C2 U2 MIT Yes Details →
0.6.2 26 Aug 2015 C2 U2 MIT Yes Details →
0.6.1 23 Aug 2015 C2 U2 MIT Yes Details →
0.6.0 23 Aug 2015 C2 U2 MIT Yes Details →
0.5.4 22 Aug 2015 C2 U2 MIT Yes Details →
0.5.3 21 Aug 2015 C2 U2 MIT Yes Details →
0.5.2 21 Aug 2015 C2 U2 MIT Yes Details →
0.5.1 21 Aug 2015 C2 U2 MIT Yes Details →
0.5.0 05 Jun 2015 C2 U2 MIT Yes Details →
0.4.1 01 Dec 2014 C2 U2 MIT Yes Details →
0.4.0 01 Dec 2014 C2 U2 MIT Yes Details →
0.3.7 21 Nov 2014 C2 U2 MIT Yes Details →
0.3.6 21 Nov 2014 C2 U2 MIT Yes Details →
0.3.5 14 Nov 2014 C2 U2 MIT Yes Details →
0.3.4 14 Nov 2014 C2 U2 MIT Yes Details →
0.3.3 14 Nov 2014 C2 U2 MIT Yes Details →
0.3.2 14 Nov 2014 C2 U2 MIT Yes Details →
0.3.1 13 Nov 2014 C2 U2 MIT Yes Details →
0.3.0 13 Nov 2014 C2 U2 MIT Yes Details →
0.2.0 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.23 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.22 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.21 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.20 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.19 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.18 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.17 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.16 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.15 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.14 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.13 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.12 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.11 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.10 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.9 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.8 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.7 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.6 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.5 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.4 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.3 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.2 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.1 12 Nov 2014 C2 U2 MIT Yes Details →
0.1.0 12 Nov 2014 C2 U2 MIT Yes Details →

All 88 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for django-s3file

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-42196: django-s3file Vulnerable to Relative Path Traversal Attacks 9.9 critical 7.0.2 05 May 2026
CVE-2026-42196: django-s3file Relative Path Traversal Vulnerability 9.9 critical 7.0.2 29 Jun 2026
CVE-2022-24840: Path Traversal in django-s3file 9.1 critical 5.5.1 06 Jun 2022
CVE-2022-24840: django-s3file AWS S3 Bucket Traversal Vulnerability N/A unrated 68ccd2c621a40eb66fdd6af2be9d5fcc9c373318 09 Jun 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About django-s3file

Is django-s3file safe to use?

Vulert records 4 vulnerabilities for django-s3file in PyPI: 2 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is django-s3file's Vulert package health score?

Vulert scores django-s3file 64/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of django-s3file affected?

Yes. 7.2.0, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of django-s3file should I use?

7.2.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does django-s3file have?

4 vulnerabilities are recorded for django-s3file in the PyPI ecosystem: 2 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new django-s3file vulnerabilities disclosed?

2 vulnerabilities were recorded for django-s3file in the last 12 months, and the oldest entry in this database dates to 06 Jun 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of django-s3file are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor django-s3file for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the django-s3file version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.