How severe is GHSA-7h2m-m8vj-598h?

No CVSS score has been assigned to GHSA-7h2m-m8vj-598h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7h2m-m8vj-598h?

GHSA-7h2m-m8vj-598h affects the following packages: django (PyPI), django (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-7h2m-m8vj-598h?

Update django to 6.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7h2m-m8vj-598h is resolved across your whole dependency graph.

How do I detect GHSA-7h2m-m8vj-598h in my PyPI dependencies?

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.

How do I mitigate GHSA-7h2m-m8vj-598h 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-7h2m-m8vj-598h?

O3 pinpoints whether GHSA-7h2m-m8vj-598h 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-7h2m-m8vj-598h actively exploited in the wild?

No public exploit code has been indexed for GHSA-7h2m-m8vj-598h 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 type of vulnerability is GHSA-7h2m-m8vj-598h?

GHSA-7h2m-m8vj-598h is classified as CWE-539 (CWE-539). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-7h2m-m8vj-598h published, and has it been updated?

GHSA-7h2m-m8vj-598h was published on May 5, 2026 and was last updated on June 5, 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-7h2m-m8vj-598h

GHSA-7h2m-m8vj-598h is a CWE-539 vulnerability in django. O3 Security confirms whether GHSA-7h2m-m8vj-598h is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Django Uses Persistent Cookies Containing Sensitive Information

Also known asBIT-django-2026-35192CVE-2026-35192PYSEC-2026-50

Published

May 5, 2026

Updated

Jun 5, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐍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

An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. Response headers do not vary on cookies if a session is not modified, but SESSION_SAVE_EVERY_REQUEST is True. A remote attacker can steal a user's session after that user visits a cached public page. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.

Django thanks Cantina for reporting this issue.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django`	≥ 6.0&&< 6.0.5	6.0.5
🐍PyPI	`django`	≥ 5.2&&< 5.2.14	5.2.14

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update django to 6.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7h2m-m8vj-598h 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-7h2m-m8vj-598h 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-7h2m-m8vj-598h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. Response headers do not vary on cookies if a session is not modified, but `SESSION_SAVE_EVERY_REQUEST` is `True`. A remote attacker can steal a user's session after that user visits a cached public page. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django thanks Cantina for reporting this issue.

O3 Security · Impact-Aware SCA

Is GHSA-7h2m-m8vj-598h in your dependencies?

O3 detects GHSA-7h2m-m8vj-598h 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