Vulnerability Database · PyPI · django-s3file · Version
django-s3file 3.0.2
3.0.2 is affected by 4 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 7.2.0.
Critical 3 High 0 Medium 0 Low 0 Unrated 1
-
Released 13 Sep 2017
Licence MIT
Also known from other sources 4
Newer releases 88
Database updated 23/Oct/2026
Release and licence data published by PyPI. 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 Vulnerabilities affecting this version
django-s3file 3.0.2 vulnerabilities
4 vulnerabilities cover django-s3file 3.0.2. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2026-42196: django-s3file Relative Path Traversal Vulnerability | 9.9 critical | 7.0.2 | 29 Jun 2026 |
| CVE-2026-42196: django-s3file Vulnerable to Relative Path Traversal Attacks | 9.9 critical | 7.0.2 | 05 May 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 |
Looking for another version, or everything Vulert holds for django-s3file?
Questions
About django-s3file 3.0.2
Is django-s3file 3.0.2 vulnerable?
Yes. 4 vulnerabilities in the Vulert database cover django-s3file 3.0.2: 3 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The upgrade Vulert recommends is 7.2.0, and each entry above names the fixed version to move to.
Which version of django-s3file should I use instead of 3.0.2?
7.2.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 3.0.2 the latest release of django-s3file?
No. 3.0.2 was published 13 Sep 2017, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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.