Skip to content
OpenAdvisories

Weakness (CWE)

CWE-524: Use of Cache Containing Sensitive Information

Base Incomplete

The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.

How to prevent it (3 mitigations)
  1. Architecture and Design

    Protect information stored in cache.

  2. Architecture and Design

    Do not store unnecessarily sensitive information in the cache.

  3. Architecture and Design

    Consider using encryption in the cache.

Source: MITRE CWE-524

17 results · Clear filters · Feed

  • Low 3.1

    Potential exposure of private data via empty and missing Vary headers

    An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19. The `django.middleware.cache.UpdateCacheMiddleware` and the `django.views.decorators.cache.cache_page()` decorator generate identical cache keys for requests that om…

  • Low 3.5

    Use of Cache Containing Sensitive Information in GitLab

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.0 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when a merge request in a public project referenced a confidential issue from a private project, an authenticated u…

  • Low 3.7

    SpeedyCache <= 1.4.2 - Unauthenticated Sensitive Information Exposure via Insecure Cache Configuration via Cache Write Gate Missing comment_author_* Cookie Check

    The SpeedyCache – Cache, Optimization, Performance plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.4.2 via the 'comment_author_*, comment_author_email_*' parameter. This makes it possible for unauth…

  • Low 3.1

    vLLM: Harmony tool continuations drop `cache_salt` — restoring a cross-tenant prefix-cache membership oracle

    vLLM is an inference and serving engine for large language models. Prior to 0.30.0, Harmony tool continuations submitted through "POST /v1/responses" requests rebuild the next-turn engine input without preserving the cache_salt value, placing the continuation…

  • Low 1.7

    PAN-OS: Information Disclosure Vulnerability in Management Web Interface

    An information disclosure vulnerability in Palo Alto Networks PAN-OS® software enables an unauthenticated attacker with network access to the management web interface to obtain web session tokens. This requires a legitimate user to first click on a malicious …

  • Low 3.5

    Open WebUI: Cross-user model-list exposure via static cache key in get_all_models (aiocache key= vs key_builder= misuse)

    Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.6.27 before 0.10.0, get_all_models handlers in routers/openai.py and routers/ollama.py passed a lambda to aiocache key instead of key_builder, causing permission-filt…

  • Low 3.1

    Potential exposure of private data via missing Vary: Authorization in UpdateCacheMiddleware

    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 add `Authorization` to the `Vary` response header for requests bearing that header without `Cache-Control: public`, wh…

  • Low 3.1

    Static resource cache poisoning in Spring MVC and WebFlux

    Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources. More precisely, an application can be vulnerable when all the following are true: * the application is using Spring MVC or Spring WebFlux * the application …

  • Low 2.3

    Flask session does not add `Vary: Cookie` header when accessed in some ways

    Flask is a web server gateway interface (WSGI) web application framework. In versions 3.1.2 and below, when the session object is accessed, Flask should set the Vary: Cookie header., resulting in a Use of Cache Containing Sensitive Information vulnerability. …

  • Low 3.1

    Umbraco.Forms CDN may cache sensitive form uploads when processed by ImageSharp

    ### Impact Protected files uploaded through Umbraco Forms may be served to unauthenticated users when a CDN or caching layer is present and ImageSharp processes the request. ImageSharp sets aggressive cache headers by default, which can cause intermediary cac…

  • Low 2.4

    The issue was addressed with improved handling of caches. This issue is fixed in macOS Sequoia 15.7.2, macOS Sonoma 14.…

  • Low 3.3

    Android App "Brother iPrint&Scan" versions 6.13.7 and earlier improperly uses an external cache directory. If exploited…

  • Low 3.3
    CVE-2025-65681 Public exploit

    Overhang Tutor Discloses Sensitive Information due to Improper Cache-Control

    An issue was discovered in Overhang.IO (tutor-open-edx) (overhangio/tutor) 20.0.2 allowing local unauthorized attackers to gain access to sensitive information due to the absence of proper cache-control HTTP headers and client-side session checks.

  • Low 3.2

    HCL Domino Volt and Domino Leap are affected by missing "no cache" headers

    Missing "no cache" headers in HCL Leap permits sensitive data to be cached.

  • Low 3.2

    HCL Leap is affected by missing "no cache" headers

    Missing "no cache" headers in HCL Leap permits user directory information to be cached.

  • Low 3.2

    HCL Leap is affected by missing "no cache" headers

    Missing "no cache" headers in HCL Leap permits sensitive data to be cached.

  • Low 3.3

    kubectl creates world-writeable cached schema files

    In Kubernetes v1.8.x-v1.14.x, schema info is cached by kubectl in the location specified by --cache-dir (defaulting to $HOME/.kube/http-cache), written with world-writeable permissions (rw-rw-rw-). If --cache-dir is specified and pointed at a different locati…