Django up to 5.2.13/6.0.4 django.middleware.cache.UpdateCacheMiddleware cache containing sensitive information
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Django up to 5.2.13/6.0.4 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component django.middleware.cache.UpdateCacheMiddleware. The manipulation results in use of cache containing sensitive information. This vulnerability was named CVE-2026-6907. The attack may be performed from remote. There is no available exploit. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Django up to 5.2.13/6.0.4. Affected is an unknown code of the component django.middleware.cache.UpdateCacheMiddleware. The manipulation with an unknown input leads to a use of cache containing sensitive information vulnerability. CWE is classifying the issue as CWE-524. The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere. This is going to have an impact on confidentiality. CVE summarizes:
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.
The advisory is available at docs.djangoproject.com. This vulnerability is traded as CVE-2026-6907 since 04/23/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 05/06/2026). This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
The vulnerability scanner Nessus provides a plugin with the ID 312274 (Linux Distros Unpatched Vulnerability : CVE-2026-6907), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.2.14 or 6.0.5 eliminates this vulnerability. The upgrade is hosted for download at docs.djangoproject.com.
The vulnerability is also documented in the vulnerability database at Tenable (312274). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.3
CNA Vector (DSF): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Use of cache containing sensitive informationCWE: CWE-524
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 312274
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-6907
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Django 5.2.14/6.0.5
Timeline
04/23/2026 CVE reserved05/05/2026 Advisory disclosed
05/05/2026 VulDB entry created
05/06/2026 VulDB entry last update
Sources
Advisory: docs.djangoproject.comStatus: Confirmed
CVE: CVE-2026-6907 (🔒)
GCVE (CVE): GCVE-0-2026-6907
GCVE (VulDB): GCVE-100-361218
Entry
Created: 05/05/2026 19:42Updated: 05/06/2026 23:42
Changes: 05/05/2026 19:42 (76), 05/06/2026 23:42 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.