HarborGuardharborguardDatabase
Back to search
CRITICALCVE-2026-53874Published Modified CNA VulnCheck

CVE-2026-53874: picklescan - Arbitrary Code Execution via Obfuscated eval Call

picklescan before 1.0.1 contains an unsafe deserialization vulnerability allowing unauthenticated users to execute arbitrary code by hiding eval calls nested under callable objects via getattr. Attackers can embed malicious code in pickle files that evades detection but executes when the pickle is loaded from untrusted sources.

Metrics

CVSS v4.0
9.3
Severity
CRITICAL
Fixed in
1.0.1
Affected Products
1

Get notified

Email me when this CVE is updated: new fix versions, severity changes, or any record change.

HarborGuard Analysis

Synopsis

An arbitrary code execution vulnerability exists in picklescan, a tool used to detect malicious pickle files. The flaw is reachable over the network, requires no authentication, and no victim interaction, based on the CVSS v4.0 vector (AV:N/PR:N/UI:N). An attacker can craft a pickle file that embeds obfuscated eval calls nested under callable objects via getattr, bypassing picklescan's detection and executing arbitrary code when the file is loaded. A patched-image rebuild at version 1.0.1 is available on HarborGuard for environments running an affected version.

HarborGuard Coverage

Detection

Detection is available across every HarborGuard environment: the CVE is ingested from upstream advisory feeds within minutes of publication and matched against customer images in connected registries and CI/CD pipelines, including custom-built images that bundle picklescan directly. Any image layer containing picklescan below version 1.0.1 is flagged automatically.

Available
Triage

HarborGuard scores this finding at CVSS 9.3 Critical and is capable of weighting that score against each environment's compliance policy to determine urgency. Triage findings are routed to the appropriate team inbox within each customer organization based on configured ownership rules.

Available
Patch

A patched-image rebuild pinned to picklescan 1.0.1 becomes available on HarborGuard for any environment where an affected image is detected. For customers with auto-remediation enabled, HarborGuard rebuilds the image, runs a regression test suite, and opens a pull request against affected workloads automatically.

Available

Exploit Conditions

  • Network reachabilityRequired

    The attacker must be able to deliver a crafted pickle file to the target service over the network, exposing any internet-accessible or network-reachable endpoint that loads pickle input.

  • AuthenticationNot required

    No credentials or session tokens are needed; the attack can be triggered by any unauthenticated party who can supply a pickle file to the affected application.

  • Victim interactionNot required

    Exploitation is automatic upon the application loading the malicious pickle file; no user click, approval, or other interaction is required.

  • Attack complexityDetail

    The exploit is reliable and condition-free: no race conditions, specific memory layouts, or environmental prerequisites are needed to trigger code execution.

Blast Radius

  • Executes arbitrary OS commands or spawns processes under the identity of the service loading the pickle file.
  • Reads any files, environment variables, or secrets accessible to that process, including API keys and credentials mounted in the container.
  • Writes or overwrites files on the container filesystem, enabling persistent backdoor installation or data corruption.
  • Crashes or degrades the affected service by consuming resources or corrupting application state.

How HarborGuard Handles This

Available on HarborGuard: detection for CVE-2026-53874 is active across all connected environments, matching any image layer that includes picklescan below 1.0.1. For environments where an affected image is identified, a rebuild at picklescan 1.0.1 is available immediately. For customers with auto-remediation enabled, HarborGuard rebuilds the affected image, executes a regression run to verify functional integrity, and opens a pull request against impacted workloads; the median time from CVE publication to merged patch PR for critical-severity issues is around 90 minutes in environments with auto-remediation enabled. Where compliance policy requires manual approval before remediation, the finding is queued at Critical priority in the appropriate team inbox for human review. No additional compensating controls are required once the patched image is deployed, but customers who need lead time before patching should consider restricting the sources from which pickle files are accepted at the application layer.

See how HarborGuard automates this

Fix available

1.0.1
Affected packages
  • picklescan / picklescan
    < 1.0.1 (from 0)
    Fixed in 1.0.1
CVSS Vector
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