VulnerabilityPublished 5 May 2026

CVE-2026-6907: djangoproject Django · Use of Cache Containing Sensitive Information

Affects djangoproject DjangoSource CVE Database V5

Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 4.3 Medium : upgrade to 6.0.5 or 5.2.14 when convenient.

Data as of 2 Nov 2026, 22:58 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.0.5, 5.2.14

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

usn-8848-1

What to do

Upgrade Django and django to 6.0.5 or 5.2.14.

Affected software

Product	Affected	Fixed in
djangoprojectDjango	Affected >=6.0 <6.0.5	Fixed in 6.0.5
djangoprojectDjango	Affected >=5.2 <5.2.14	Fixed in 5.2.14
PyPIdjango`pkg:pypi/django`Other threats	Affected =6.0 <6.0.5 <5.2.14	Fixed in 6.0.5 5.2.14
PyPIdjango`pkg:pypi/django`Other threats	Affected >=6.0 <6.0.5 >=5.2 <5.2.14	Fixed in 6.0.5 5.2.14

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is confirmed, avoid configurations that cause the Vary header to contain an asterisk or disable caching middleware if feasible to reduce risk.

Description

Bence Nagy discovered that GeoDjango in Django incorrectly handled spatial lookups when processing untrusted input. A remote attacker could possibly use this issue to make outbound network requests, write arbitrary files, or execute arbitrary code. This issue was only addressed in Ubuntu 22.04 LTS, Ubuntu 24.04 LTS and Ubuntu 26.04 LTS. (CVE-2026-15307) Ahmad Sadeddin discovered that Django UpdateCacheMiddleware incorrectly cached requests where the Vary header contained an asterisk. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2026-6907) Ahmed Badawe discovered that Django did not properly parse Cache-Control response directives case-insensitively under certain circumstances. A remote attacker could possibly use this issue to view sensitive information from responses that were incorrectly cached. This issue only affected Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and Ubuntu 26.04 LTS. (CVE-2026-8404)

Impact

The vulnerability can cause private data to be cached and served incorrectly, potentially exposing sensitive information to unauthorized parties. However, the CVSS score of 4.3 indicates a medium impact primarily affecting confidentiality, with no impact on integrity or availability. There are no known active exploits in the wild at this time.

Summary

CVE-2026-6907 is a medium severity vulnerability in Django's UpdateCacheMiddleware that causes it to cache HTTP responses even when the Vary header includes an asterisk ('*'). This leads to the unintended caching of sensitive information, potentially exposing private data to unauthorized users. The flaw affects Django versions 6.0 prior to 6.0.5 and 5.2 prior to 5.2.14, with earlier unsupported versions possibly impacted. The vulnerability is categorized under CWE-524, which involves the use of caches containing sensitive information.

CWE-524Use of Cache Containing Sensitive Information (opens in a new tab)
Base weakness
The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.
Architecture and Design
Protect information stored in cache.
Architecture and Design
Do not store unnecessarily sensitive information in the cache.
Architecture and Design
Consider using encryption in the cache.
OWASP ASVS 4.0.3
V8.1.1 (opens in a new tab)
V8.1.2 (opens in a new tab)
Attack patterns
Lifting Sensitive Data Embedded in Cache (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 May 2026, 03:48 UTC

WeaknessesCWE-524

Technical details

References

Community reviews

Related threats