Skip to content

← Public intelligence

PyPI package

django-s3file

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Critical, CVSS 9.9PyPIAmendedPublished

    django-s3file is vulnerable to relative path traversal

    CVE-2026-42196 · GHSA-67qg-7284-2277

    Affected
    • PyPI django-s3file < 7.0.2
    Fixed in
    7.0.2· Vendor fix available
    Issue
    Impact `S3FileMiddleware` is vulnerable to relative path traversal attacks, where an attacker can use a modified request to escape pre-signed upload locations and have the Django application load files from random locations into `request.FILES` Depending on how files are handled, this may lead to confidentiality and integrity issues. Patches Django-S3File urges all users to update to a patched version >=7.0.2.

    Recommended action: Upgrade to 7.0.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.com (1)osv.dev (2)Source checked Evidence →
  2. Critical, CVSS 9.3PyPIAmendedPublished

    Path Traversal in django-s3file

    CVE-2022-24840 · GHSA-4w8f-hjm9-xwgf

    Affected
    • PyPI django-s3file < 5.5.1
    Fixed in
    5.5.1· Vendor fix available
    Issue
    Impact It was possible to traverse the entire AWS S3 bucket and in most cases to access or delete files. The issue was discovered by the maintainer. There were no reports of the vulnerability being known to or exploited by a third party, before the release of the patch. If the AWSLOCATION setting was set, traversal was limited to that location only. If all your files handling views (like form views) require authentication or special permission, the thread is limited to privileged users. Patches The vulnerability has been fixed in version 5.5.1 and above. Workarounds There is no feasible workaround. We must urge all users to immediately updated to a patched version. Detailed attack vector description An attacker may use a request with malicious form data to traverse the entire AWS S3 bucket and perform destructive operations. An attack could look as follows: This will result in a request with files set and opened: Since this behavior is injected via a middleware, any view can be…

    Recommended action: Upgrade to 5.5.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →