LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69872: DiskCache (python-diskcache) through 5.6.3 uses Python pickle for serialization by default.

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

DiskCache for Python stores cached data using pickle by default through version 5.6.3. If an attacker can write into the cache directory, a later application read can execute attacker-controlled code. This is critical where cache storage is shared, writable, or exposed through another flaw.

Executive priority

Prioritize review for internet-facing or multi-tenant Python services, especially where local file permissions are weak. Business urgency is high because successful exploitation can mean full application compromise, but risk depends on attacker write access to the cache directory.

Technical view

The issue is unsafe Python pickle deserialization in python-diskcache through 5.6.3. The stated execution path requires attacker write access to the cache directory and a victim application cache read. The CVE maps to CWE-502 and CWE-94 with CVSS 9.8, but affected CPE/product metadata is incomplete in the supplied record.

Likely exposure

Exposure is most likely in Python services using DiskCache through 5.6.3 where cache files can be modified by untrusted users, workloads, compromised accounts, or adjacent applications.

Exploitation context

The bundle does not show KEV listing or cited evidence of active exploitation. The described attack condition is specific: attacker write access to cache storage, followed by a victim application reading the poisoned cache entry.

Researcher notes

The supplied record lacks precise affected package metadata and does not include a confirmed upstream patch version. Validate real-world exposure by dependency usage and cache write boundaries, not CVSS alone. Avoid assuming network-only exploitability without the required cache write primitive.

Mitigation direction

  • Check upstream DiskCache and Red Hat advisory guidance for fixed package or configuration direction.
  • Audit and restrict write permissions on all DiskCache cache directories.
  • Remove untrusted or attacker-writable cache storage from production application paths.
  • Clear cache directories that may have been writable by untrusted parties.
  • Apply relevant Red Hat errata where Red Hat-packaged components are in use.

Validation and detection

  • Inventory Python applications and dependencies for python-diskcache usage.
  • Identify deployed DiskCache versions and flag versions through 5.6.3.
  • Review cache directory ownership, permissions, mounts, and sharing boundaries.
  • Confirm whether untrusted users or processes can write cache files.
  • Check Red Hat package status against the cited CVE and errata.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-69872 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP
7.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L2.15.5redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-69872Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPpython-diskcache: python-diskcache: Arbitrary code execution via insecure pickle deserialization
other:Red Hat severity ratingcvssV3_1
  • 2026-02-11T19:01:01.798Z: Reported to Red Hat.
  • 2026-02-11T00:00:00.000Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-502CWE-94

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.