CVE Intelligence
Analysis AI-assisted

CVE-2026-56315: picklescan: unblocked standard library modules allow remote code execution

picklescan versions before 1.0.4 fail to block at least seven Python standard library modules that expose eight functions capable of direct command execution. According to the record, a crafted pickle file importing these modules could lead to remote code execution while bypassing the scanner's safety validation. The CNA VulnCheck reports a CVSS 3.1 base score of 9.8 (critical); no confirmed exploitation appears in the sources consulted.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Ler em português

Overview

Picklescan is a tool that scans Python pickle files for dangerous content. According to the record, versions before 1.0.4 fail to block at least seven Python standard library modules that expose eight functions providing direct command execution. The weakness is classified as CWE-184, an incomplete list of disallowed inputs.

Impact

  • The record states that the gap can lead to remote code execution when a malicious pickle file imports one of the unblocked modules.
  • The record states that the scanner's safety validation can be bypassed for these modules.
  • The CNA VulnCheck reports a CVSS 3.1 base score of 9.8 (critical) and a CVSS 4.0 score of 9.3.

Affected products and versions

  • Product: picklescan, versions before 1.0.4 according to the record.
  • The record's affected list is empty, so package coordinates and vendor entries are unknown from the record alone. The advisories linked below should be consulted for details.

Exploitation status

The record shows this CVE is not listed in the CISA KEV catalog. No confirmed exploitation appears in the sources consulted.

Remediation and mitigation

  • Upgrade picklescan to version 1.0.4 or later. The record's wording suggests 1.0.4 is the first version outside the described range, but the record does not state this directly.
  • Until the upgrade is applied, treat pickle files from untrusted sources as hostile and avoid loading them in sensitive environments.
  • Run processes that handle pickle data with isolation and least privilege, so that a successful code execution has limited reach.
  • Do not rely on a scanner result as the only control for untrusted pickle data.

Detection guidance

  • Inventory environments that use picklescan and record the installed versions.
  • Review pipelines that ingest pickle files from external sources, such as model repositories or user uploads, and log scanner results.
  • Monitor services that deserialize pickle data for unexpected child processes or outbound network activity.

Limitations of the available information

  • The record has no fixed-version field, no affected-version list, and no EPSS score.
  • The record says 'at least seven' modules, so the full set of affected modules is unknown.
  • The CVSS 4.0 score is recorded, but the record does not include a separate vendor assessment.

Frequently asked questions

Which picklescan versions are described as affected?

The record describes versions before 1.0.4 as affected. The record does not provide a separate list of affected versions.

Is this vulnerability known to be exploited in the wild?

The record shows this CVE is not listed in the CISA KEV catalog. No confirmed exploitation appears in the sources consulted.

What is the main defensive step?

Upgrade picklescan to version 1.0.4 or later, and treat pickle files from untrusted sources as hostile until the upgrade is complete.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.