Security readout for executives and security teams
Plain-English summary
This is a high-risk flaw in picklescan, a tool used to inspect Python pickle files for dangerous behavior. Older versions may miss a malicious pickle technique, so an organization could wrongly treat a file as safe. Code execution still requires someone or some workflow to load the malicious pickle.
Executive priority
Treat as a prompt remediation item for teams handling ML models, datasets, or serialized Python artifacts. The issue is not confirmed as exploited, but it can undermine a security control and enable code execution if malicious pickle files are trusted.
Technical view
picklescan before 0.0.29 does not detect use of profile.Profile.runctx inside pickle reduce behavior. A crafted pickle can evade detection and later execute code when deserialized by a vulnerable workflow. The weakness is CWE-502 and the CVSS vector indicates network-origin input with required user interaction.
Likely exposure
Exposure is most likely in ML, data science, CI, artifact scanning, or file ingestion workflows that rely on picklescan to approve untrusted pickle files. Systems that never load pickle files, or do not rely on affected picklescan versions, have lower exposure.
Exploitation context
The source bundle does not report known active exploitation, and KEV is false. The practical risk is supply-chain or file-ingestion abuse where an attacker provides a pickle file that passes scanning, then executes when loaded by a target process.
Researcher notes
Evidence is limited to the CVE description and advisory references in the source bundle. The issue is a detection bypass in picklescan, not proof that all pickle-loading applications are directly vulnerable. Validate exposure by tracing trust decisions around scanned pickle files.
Mitigation direction
- Upgrade picklescan to 0.0.29 or later, per the affected-version description.
- Do not load pickle files from untrusted or unauthenticated sources.
- Quarantine pickle artifacts scanned by older picklescan versions until reassessed.
- Check vendor advisories for any additional fixed versions or guidance.
- Prefer safer serialization formats where pickle behavior is not required.
Validation and detection
- Inventory all environments using picklescan and record installed versions.
- Identify pipelines that scan pickle files before loading them.
- Reassess recently accepted pickle artifacts scanned with versions before 0.0.29.
- Review logs for workflows loading externally supplied pickle files.
- Confirm vendor advisory details against local package constraints.
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 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-71341 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
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
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:R/S:U/C:H/I:H/A:N2.85.2VulnCheckCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
7.6HighVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
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
- GitHub Security Advisory (GHSA-6vqj-c2q5-j97w)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: picklescan - Remote Code Execution via Undetected profile.Profile.runctxCVE 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.
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.