Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

GHSA-v6rh-hp5x-86rv

HIGHFix: django/django@d4dcd5b

GHSA-v6rh-hp5x-86rv is a high-severity (CVSS 7.3) vulnerability in django. O3 Security confirms whether GHSA-v6rh-hp5x-86rv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Potential bypass of an upstream access control based on URL paths in Django

Also known asBIT-django-2021-44420CVE-2021-44420PYSEC-2021-439
Published
Dec 9, 2021
Updated
Nov 19, 2024
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 19, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected
🐍django🐍django🐍django

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

In Django 2.2 before 2.2.25, 3.1 before 3.1.14, and 3.2 before 3.2.10, HTTP requests for URLs with trailing newlines could bypass upstream access control based on URL paths. This issue has low severity, according to the Django security policy.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIdjango2.2a1&&< 2.2.252.2.25
🐍PyPIdjango3.0a1&&< 3.1.143.1.14
🐍PyPIdjango3.2a1&&< 3.2.103.2.10

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. Fix

    Update django to 2.2.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v6rh-hp5x-86rv is resolved across your whole dependency graph.

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

  4. How O3 protects you

    O3 pinpoints whether GHSA-v6rh-hp5x-86rv 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-v6rh-hp5x-86rv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Django 2.2 before 2.2.25, 3.1 before 3.1.14, and 3.2 before 3.2.10, HTTP requests for URLs with trailing newlines could bypass upstream access control based on URL paths. This issue has low severity, according to the Django security policy.
O3 Security · Impact-Aware SCA

Is GHSA-v6rh-hp5x-86rv in your dependencies?

O3 detects GHSA-v6rh-hp5x-86rv across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-v6rh-hp5x-86rv: django (High 7.3) | O3 Security