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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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.

What is the EPSS score for GHSA-67qg-7284-2277?

GHSA-67qg-7284-2277 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-67qg-7284-2277?

GHSA-67qg-7284-2277 is classified as Path Traversal (CWE-22), CWE-26 (CWE-26). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data 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 October 27, 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

Not in CISA KEV

django-s3file is vulnerable to relative path traversalGHSA-67qg-7284-2277

GHSA-67qg-7284-2277 is a Path Traversal vulnerability in django-s3file. A fix is available for django-s3file — see the affected versions and patch details below.

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

Published

May 5, 2026

Updated

Oct 27, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-67qg-7284-2277.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django-s3file`	all versions	7.0.2`pip install --upgrade 'django-s3file==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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works