How severe is GHSA-6r3c-8xf3-ggrr?

No CVSS score has been assigned to GHSA-6r3c-8xf3-ggrr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6r3c-8xf3-ggrr?

GHSA-6r3c-8xf3-ggrr affects the following packages: django-sendfile2 (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-6r3c-8xf3-ggrr?

Update django-sendfile2 to 0.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6r3c-8xf3-ggrr is resolved across your whole dependency graph.

How do I detect GHSA-6r3c-8xf3-ggrr in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django-sendfile2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6r3c-8xf3-ggrr 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-6r3c-8xf3-ggrr?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6r3c-8xf3-ggrr can be triaged on real exposure rather than presence alone.

Is GHSA-6r3c-8xf3-ggrr actively exploited in the wild?

No public exploit code has been indexed for GHSA-6r3c-8xf3-ggrr 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-6r3c-8xf3-ggrr published, and has it been updated?

GHSA-6r3c-8xf3-ggrr was published on June 24, 2020 and was last updated on December 2, 2024. 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

GHSA-6r3c-8xf3-ggrr — django-sendfile2

Fix: moggers87/django-sendfile2@f870c52

GHSA-6r3c-8xf3-ggrr is a security vulnerability in django-sendfile2. A fix is available for django-sendfile2 — see the affected versions and patch details below.

Directory traversal outside of SENDFILE_ROOT in django-sendfile2

Published

Jun 24, 2020

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍django-sendfile2

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-sendfile2 currently relies on the backend to correctly limit file paths to SENDFILE_ROOT. This is not the case for the simple and development backends, it is also not necessarily the case for any of the other backends either (it's just an assumption that was made by the original author).

This will be fixed in 0.6.0 which is to be released the same day as this advisory is made public.

When upgrading, you will need to make sure SENDFILE_ROOT is set in your settings module if it wasn't already.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django-sendfile2`	all versions	0.6.0`pip install --upgrade 'django-sendfile2==0.6.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django-sendfile2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update django-sendfile2 to 0.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6r3c-8xf3-ggrr 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6r3c-8xf3-ggrr can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6r3c-8xf3-ggrr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

django-sendfile2 currently relies on the backend to correctly limit file paths to `SENDFILE_ROOT`. This is not the case for the `simple` and `development` backends, it is also not necessarily the case for any of the other backends either (it's just an assumption that was made by the original author). This will be fixed in 0.6.0 which is to be released the same day as this advisory is made public. When upgrading, you will need to make sure `SENDFILE_ROOT` is set in your settings module if it wasn't already.

O3 Security · Impact-Aware SCA

Is GHSA-6r3c-8xf3-ggrr in your dependencies?

O3 Security finds GHSA-6r3c-8xf3-ggrr across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works