GHSA-m6gj-h9gm-gw44 is a high-severity (CVSS 7.5) Incorrect Default Permissions vulnerability in django. O3 Security confirms whether GHSA-m6gj-h9gm-gw44 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Django Incorrect Default Permissions
Real-World Exposure
django🐍django🐍djangoReal-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
An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). FILE_UPLOAD_DIRECTORY_PERMISSIONS mode was not applied to intermediate-level directories created in the process of uploading files. It was also not applied to intermediate-level collected static directories when using the collectstatic management command.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django | ≥ 2.2a1&&< 2.2.16 | 2.2.16 |
| 🐍PyPI | django | ≥ 3.0a1&&< 3.0.10 | 3.0.10 |
| 🐍PyPI | django | ≥ 3.1a1&&< 3.1.1 | 3.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django. 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 to 2.2.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m6gj-h9gm-gw44 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-m6gj-h9gm-gw44 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-m6gj-h9gm-gw44. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Frequently Asked Questions
Is GHSA-m6gj-h9gm-gw44 in your dependencies?
O3 detects GHSA-m6gj-h9gm-gw44 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.