Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-8404 low CVSS 3.1

Vulnerability in django (CVE-2026-8404)

Summary

Vulnerability in django (CVE-2026-8404). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.2.15, 6.0.6 or later.

Original description

The description as published by the source.

An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6.
django.middleware.cache.UpdateCacheMiddleware in Django does not match Cache-Control response directives case-insensitively, which allows remote attackers to read responses that were incorrectly cached because their Cache-Control directives used uppercase or mixed-case values.
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 would like to thank Ahmed Badawe for reporting this issue.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-8404 has been found in django.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: upgrade django to 5.2.15, 6.0.6 or later.
If unsure, ask your IT team or search "django CVE-2026-8404" on the vendor's site.

CVE-2026-8404 (django) — CWE-178 / CVSS v3 3.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.2.15, 6.0.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-178) exists in django.

📍 Affected scope

Check the vendor advisory for the affected versions of django.

🔥 Severity

Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.2.15, 6.0.6.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'django' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'django' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で django を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade django to 5.2.15, 6.0.6

    ステージング環境で 5.2.15, 6.0.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami django
[{"type":"SEMVER","events":[{"introduced":"5.2.0"},{"fixed":"5.2.15"},{"introduced":"6.0.0"},{"fixed":"6.0.6"}]}]
PyPI django
[{"type":"ECOSYSTEM","events":[{"introduced":"5.2"},{"fixed":"5.2.15"},{"introduced":"6.0"},{"fixed":"6.0.6"}]}]
pip django
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.0.6"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details