Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.3amended

Path Traversal in django-s3file

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

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (django-s3file 5.5.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2022-24840: 2.07% estimated exploitation activity in the next 30 days; percentile 81.42 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-4w8f-hjm9-xwgf

  2. Revision 3 · amended ·

    Amended from ghsa record GHSA-4w8f-hjm9-xwgf

  3. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  4. Revision 1 · created ·

    Published from osv record GHSA-4w8f-hjm9-xwgf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-24840

Advisory: Path Traversal in django-s3file
IDs: CVE-2022-24840, GHSA-4w8f-hjm9-xwgf
Record: https://patchnext.com/advisories/cve-2022-24840 (revision 4, source checked 28 Oct 2026, 13:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: django-s3file 5.5.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI django-s3file: affected < 5.5.1; fixed in 5.5.1

## Suggested inspection (read-only)
- `python -m pip show django-s3file`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on django-s3file.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-4w8f-hjm9-xwgf (OSV record GHSA-4w8f-hjm9-xwgf lists affected ranges: PyPI django-s3file >=0 <5.5.1 (fixed))
- Verified: https://github.com/advisories/GHSA-4w8f-hjm9-xwgf (GitHub-reviewed advisory GHSA-4w8f-hjm9-xwgf lists affected ranges: PyPI django-s3file >=0 <5.5.1)

Commands are suggestions: review each one before running it.

Loading voting…