How severe is GHSA-67qg-7284-2277?

No CVSS score has been assigned to GHSA-67qg-7284-2277 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-67qg-7284-2277?

GHSA-67qg-7284-2277 affects the following packages: django-s3file (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-67qg-7284-2277?

Update django-s3file to 7.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67qg-7284-2277 is resolved across your whole dependency graph.

How do I detect GHSA-67qg-7284-2277 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django-s3file. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-67qg-7284-2277 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-67qg-7284-2277?

O3 pinpoints whether GHSA-67qg-7284-2277 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-67qg-7284-2277 actively exploited in the wild?

No public exploit code has been indexed for GHSA-67qg-7284-2277 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-67qg-7284-2277 published, and has it been updated?

GHSA-67qg-7284-2277 was published on May 5, 2026 and was last updated on June 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-67qg-7284-2277

GHSA-67qg-7284-2277 is a security vulnerability in django-s3file. O3 Security confirms whether GHSA-67qg-7284-2277 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

django-s3file is vulnerable to relative path traversal

Also known asCVE-2026-42196PYSEC-2026-328

Published

May 5, 2026

Updated

Jun 29, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

🐍django-s3file

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django-s3file`	all versions	7.0.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django-s3file. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update django-s3file to 7.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67qg-7284-2277 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-67qg-7284-2277 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-67qg-7284-2277. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-67qg-7284-2277 in your dependencies?

O3 detects GHSA-67qg-7284-2277 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works