dbcve.org
DjangoFramework / library · Djangoproject

CVE-2026-6907

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-05
Fix available
A fix is available. Upgrade to 5.2.14 / 6.0.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. `django.middleware.cache.UpdateCacheMiddleware` erroneously caches requests where the `Vary` header contained an asterisk (`'*'`). This can lead to private data being stored and served. 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 Ahmad Sadeddin for reporting this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Django's UpdateCacheMiddleware incorrectly caches HTTP responses when the Vary header contains an asterisk ('*'). The Vary: * header signals that a response should not be cached because it varies based on multiple request characteristics, but Django was storing these responses anyway, leading to private or user-specific data being cached and potentially served to other users.

MitigationUpgrade Django to version 6.0.5, 5.2.14, or later to patch the middleware logic. Alternatively, audit and temporarily disable UpdateCacheMiddleware on sensitive endpoints until the upgrade can be performed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DjangoFramework / library
Affected:>= 5.2, < 5.2.14>= 6.0, < 6.0.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Django version
    Run `python -c 'import django; print(django.get_version())'` or check your requirements.txt/poetry.lock file
    Affected if The version is >= 5.2 but < 5.2.14, or >= 6.0 but < 6.0.5
  2. Verify UpdateCacheMiddleware is enabled
    Check your Django settings file for MIDDLEWARE or MIDDLEWARE_CLASSES and confirm 'django.middleware.cache.UpdateCacheMiddleware' is listed
    Affected if UpdateCacheMiddleware is present in the middleware stack
  3. Confirm caching is configured
    Check for a non-empty CACHES setting in your Django settings (e.g., CACHES = {'default': {'BACKEND': '...'}})
    Affected if Caching is enabled with any backend (locmem, redis, database, etc.)
  4. Identify endpoints using Vary header
    Search your codebase for responses setting Vary header with '*' (e.g., response['Vary'] = '*' or @vary_on_headers('*'))
    Affected if Any view or code explicitly sets Vary: * on cached responses

You are affected if your Django version falls within the vulnerable range AND UpdateCacheMiddleware is active AND caching is enabled, because responses intended to remain private (Vary: *) would be incorrectly stored in cache and potentially served to other users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.2.14 / 6.0.5 or later
Fixed in 5.2.146.0.5
Interim mitigation

Upgrade Django to version 6.0.5, 5.2.14, or later to patch the middleware logic. Alternatively, audit and temporarily disable UpdateCacheMiddleware on sensitive endpoints until the upgrade can be performed.

Recommended fix High confidence

Django 5.2.14 or Django 6.0.5 (depending on your major version)

  1. 1. Identify your current Django version by running `django --version` or checking your requirements file
  2. 2. For Django 5.2.x: Upgrade to version 5.2.14 or later using pip: `pip install 'Django>=5.2.14'`
  3. 3. For Django 6.0.x: Upgrade to version 6.0.5 or later using pip: `pip install 'Django>=6.0.5'`
  4. 4. After upgrading, verify the installation: `django --version`
  5. 5. Run your test suite to ensure the application functions correctly after the upgrade
  6. 6. If you encounter issues, review the Django release notes for any breaking changes between your version and the target version
Caveat Django minor version upgrades typically have minimal breaking changes, but review the release notes for your specific version jump for any deprecation warnings or behavior changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Django Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,100
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,360.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6907 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6907 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data