dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-53874

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

picklescan before 1.0.1 contains an unsafe deserialization vulnerability where attackers can embed malicious code in pickle files using getattr-wrapped eval calls that evade the scanner's detection mechanisms but execute arbitrary code when the pickle is loaded from untrusted sources.

MitigationUpgrade to picklescan 1.0.1 or later, and avoid loading pickle files from untrusted sources regardless of scan results.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if picklescan is installed
    Run 'pip list' or 'pip show picklescan' to see if the picklescan package is present in your Python environment
    Affected if picklescan is not installed - the vulnerability does not apply since the vulnerable software is not present
  2. Determine installed picklescan version
    Run 'pip show picklescan' or 'pip list | grep picklescan' to identify the exact version number
    Affected if version is present but less than 1.0.1 (e.g., 1.0.0, 0.9.x, etc.) - the unsafe deserialization bypass vulnerability exists in this version
  3. Verify if picklescan is used on untrusted pickle files
    Review your workflows, scripts, or automation that invoke picklescan to determine whether it processes pickle files from untrusted or user-controlled sources (e.g., uploaded files, external APIs, network endpoints)
    Affected if picklescan < 1.0.1 is used to scan pickle files from untrusted sources - the scanner can be evaded by getattr-wrapped eval payloads while the pickle will execute arbitrary code when loaded

You are affected if picklescan version is below 1.0.1 AND you use it to scan pickle files from untrusted or unverified sources, as the scanner can miss malicious payloads that will execute upon pickle deserialization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to picklescan 1.0.1 or later, and avoid loading pickle files from untrusted sources regardless of scan results.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53874 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53874 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data