PYSEC-2026-2447

Vulnerability from pysec - Published: 2026-07-13 14:36 - Updated: 2026-07-13 16:03
VLAI
Details

DiskCache (python-diskcache) through 5.6.3 uses Python pickle for serialization by default. An attacker with write access to the cache directory can achieve arbitrary code execution when a victim application reads from the cache.

Impacted products
Name purl
diskcache pkg:pypi/diskcache

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "diskcache",
        "purl": "pkg:pypi/diskcache"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "5.6.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.1.0",
        "0.1.2",
        "0.1.3",
        "0.1.4",
        "0.1.5",
        "0.1.6",
        "0.1.7",
        "0.1.8",
        "0.2.0",
        "0.2.1",
        "0.2.10",
        "0.2.2",
        "0.2.3",
        "0.2.4",
        "0.2.6",
        "0.2.7",
        "0.2.8",
        "0.2.9",
        "0.3.0",
        "0.3.1",
        "0.4.0",
        "0.5.0",
        "0.6.0",
        "0.7.0",
        "0.7.1",
        "0.9.0",
        "1.0.0",
        "1.1.0",
        "1.2.0",
        "1.3.1",
        "1.3.3",
        "1.3.4",
        "1.3.5",
        "1.4.0",
        "1.5.0",
        "1.5.2",
        "1.5.3",
        "1.6.0",
        "1.6.1",
        "1.6.2",
        "1.6.3",
        "1.6.4",
        "1.6.5",
        "1.6.6",
        "1.6.7",
        "1.7.0",
        "2.0.2",
        "2.1.0",
        "2.2.0",
        "2.3.0",
        "2.3.1",
        "2.4.0",
        "2.4.1",
        "2.5.1",
        "2.5.2",
        "2.6.0",
        "2.6.4",
        "2.6.5",
        "2.7.0",
        "2.8.2",
        "2.8.3",
        "2.9.0",
        "3.0.0",
        "3.0.1",
        "3.0.3",
        "3.0.4",
        "3.0.5",
        "3.0.6",
        "3.1.0",
        "3.1.1",
        "4.0.0",
        "4.1.0",
        "5.0.0",
        "5.0.1",
        "5.0.2",
        "5.0.3",
        "5.1.0",
        "5.2.1",
        "5.3.0",
        "5.4.0",
        "5.5.1",
        "5.6.0",
        "5.6.1",
        "5.6.3"
      ]
    }
  ],
  "aliases": [
    "CVE-2025-69872",
    "GHSA-w8v5-vhqr-4h9v"
  ],
  "details": "DiskCache (python-diskcache) through 5.6.3 uses Python pickle for serialization by default. An attacker with write access to the cache directory can achieve arbitrary code execution when a victim application reads from the cache.",
  "id": "PYSEC-2026-2447",
  "modified": "2026-07-13T16:03:51.854995Z",
  "published": "2026-07-13T14:36:36.004443Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69872"
    },
    {
      "type": "WEB",
      "url": "https://github.com/EthanKim88/ethan-cve-disclosures/blob/main/CVE-2025-69872-DiskCache-Pickle-Deserialization.md"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/grantjenks/python-diskcache"
    },
    {
      "type": "PACKAGE",
      "url": "https://pypi.org/project/diskcache"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-w8v5-vhqr-4h9v"
    }
  ],
  "severity": [
    {
      "score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P",
      "type": "CVSS_V4"
    }
  ],
  "summary": "DiskCache has unsafe pickle deserialization"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…