Path Traversal in django-s3file (CVE-2026-42196)
Summary
Path traversal in django-s3file (CVE-2026-42196). Risk of unauthorized operations or information disclosure. Exploitable via S3FileMiddleware. Mitigation: upgrade to 7.0.2 or later.
Original description
The description as published by the source.
django-s3file is a lightweight file upload input for Django and Amazon S3. Prior to 7.0.2, 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. This vulnerability is fixed in 7.0.2.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42196 has been found in django-s3file.
Attackers can target a specific entry point like S3FileMiddleware over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade django-s3file to 7.0.2 or later.
If unsure, ask your IT team or search "django-s3file CVE-2026-42196" on the vendor's site.
CVE-2026-42196 (django-s3file) — CWE-22
Attack surface: S3FileMiddleware / request.FILES
Patched: 7.0.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in django-s3file. Attackers reach the vulnerable code path via S3FileMiddleware.
Check the vendor advisory for the affected versions of django-s3file. Attack surface: S3FileMiddleware / request.FILES.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 7.0.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'django-s3file' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'django-s3file' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
django-s3fileを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade django-s3file to 7.0.2ステージング環境で 7.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com