Security readout for executives and security teams
Plain-English summary
CVE-2025-71323 affects picklescan, a tool used to inspect Python pickle files. Versions before 0.0.33 did not block the ctypes module, allowing a malicious pickle file to escape intended protections and run code. This is business-critical where untrusted model or pickle files are scanned automatically.
Executive priority
Prioritize remediation within emergency patch timelines for environments processing untrusted files. The vulnerability can turn a protective scanning workflow into a code-execution path. If picklescan is not used or never sees attacker-influenced files, urgency is lower but inventory should still be confirmed.
Technical view
The issue is CWE-184: incomplete disallowed input list. picklescan before 0.0.33 failed to block ctypes, enabling malicious pickle content to invoke low-level operating system capabilities and bypass sandbox or gadget-chain detection. The published CVSS is 9.8 critical, with network attack vector, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is highest in ML, data science, CI/CD, and artifact-ingestion workflows where picklescan processes files from users, partners, public repositories, or automated uploads. Systems scanning only trusted, internally generated pickle files have lower likelihood, but impact remains severe if file input can be influenced.
Exploitation context
The sources describe remote code execution through crafted pickle files and do not report active exploitation. CISA KEV status is false in the provided bundle. Treat this as a high-priority exposure because exploitation requirements are low and affected workflows often process externally supplied artifacts.
Researcher notes
The key condition is attacker influence over a pickle file processed by vulnerable picklescan. Public sources identify the bypassed module control and RCE impact but do not provide KEV-backed exploitation evidence. Validate exact dependency paths because picklescan may appear in ML supply-chain tooling rather than standard server inventories.
Mitigation direction
- Upgrade picklescan to 0.0.33 or later, as sources describe earlier versions as vulnerable.
- Pause scanning of untrusted pickle files until affected deployments are updated.
- Run scanning jobs with minimal privileges in isolated, disposable environments.
- Review vendor and advisory pages for any new mitigation or affected-version clarification.
Validation and detection
- Inventory hosts, containers, notebooks, and pipelines that install or vendor picklescan.
- Confirm deployed picklescan versions are 0.0.33 or later.
- Identify workflows that process pickle files from external or semi-trusted sources.
- Check security monitoring for suspicious activity around artifact-scanning jobs.
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-184: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-71323 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.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
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
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.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GHSA Advisory GHSA-4675-36f9-wf6rCVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: picklescan - Remote Code Execution via Unblocked ctypes ModuleCVE reference, VulnCheck · third-party-advisory
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.
Incomplete List of Disallowed Inputs
Incomplete List of Disallowed Inputs represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.