Security readout for executives and security teams
Plain-English summary
DiskCache uses Python pickle serialization by default through version 5.6.3. If an attacker can write malicious cache data, a victim application may execute code when reading the cache. Business urgency is high where cache directories are writable by untrusted users, shared services, or compromised components.
Executive priority
Treat this as urgent for internet-facing or multi-tenant Python services using DiskCache. Prioritize systems where cache files cross trust boundaries. Where DiskCache is absent or cache directories are tightly owned, urgency is lower but still requires confirmation.
Technical view
The issue is unsafe deserialization in python-diskcache, mapped to CWE-502 and CWE-94. The source bundle assigns CVSS 9.8 critical. The key condition is attacker write access to the cache directory followed by application cache reads. Affected-product metadata is incomplete in the CVE record.
Likely exposure
Exposure is most likely in Python applications using DiskCache through 5.6.3, especially where cache paths are shared, writable across privilege boundaries, or influenced by user-controlled workflows.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. It describes a plausible arbitrary code execution condition, but exploitation requires cache write access before the victim application reads cached content.
Researcher notes
Evidence is strong for the unsafe default serialization pattern and impact claim, but the bundle lacks complete affected CPE data and does not provide active exploitation evidence. Practical exploitability depends on cache write access, despite the critical CVSS score.
Mitigation direction
- Inventory applications using python-diskcache or DiskCache through 5.6.3.
- Restrict cache directory write permissions to the owning application account only.
- Remove shared or user-writable cache locations from production deployments.
- Review upstream DiskCache guidance and Red Hat advisories for supported fixes.
- Prioritize rebuilding containers or hosts that package vulnerable DiskCache versions.
Validation and detection
- Search dependency manifests and lockfiles for diskcache package versions.
- Inspect runtime configuration for DiskCache cache directory paths.
- Verify filesystem ownership and write permissions on cache directories.
- Check whether Red Hat errata apply to deployed platforms.
- Confirm no untrusted workflow can write cache entries.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCWE-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 lookupExecution 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 lookupCVE-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- 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
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L2.15.5redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
7.6HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-02-11T19:01:01.798Z: Reported to Red Hat.
- 2026-02-11T00:00:00.000Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/grantjenks/python-diskcacheCVE reference, mitre
- https://github.com/EthanKim88/ethan-cve-disclosures/blob/main/CVE-2025-69872-DiskCache-Pickle-Deserialization.mdCVE reference, mitre
- https://access.redhat.com/security/cve/CVE-2025-69872CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2439059CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-69872.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:3713CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:36350CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.