CVE-2026-56315
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 · uneditedpicklescan before 1.0.4 fails to block at least seven Python standard library modules (including uuid, _osx_support, _aix_support, _pyrepl.pager, and imaplib) exposing eight functions that provide direct arbitrary command execution. Attackers can craft malicious pickle files importing these unblocked modules to achieve remote code execution while bypassing picklescan's safety validation entirely.
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 · moderate confidencepicklescan before 1.0.4 is a Python pickle file security scanner that fails to block at least seven Python standard library modules (uuid, _osx_support, _aix_support, _pyrepl.pager, imaplib, and two others) containing eight functions that enable arbitrary command execution. Attackers can craft malicious pickle files that import these unblocked modules to achieve remote code execution, completely bypassing picklescan's safety validation.
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 checksWork through these to decide whether this CVE applies to you.
-
Check if picklescan is installedRun: pip show picklescan or pip list | grep -i picklescanAffected if picklescan is not installed - the tool is not present in the environment
-
Determine installed picklescan versionRun: pip show picklescan and note the Version fieldAffected if version is below 1.0.4 (e.g., 1.0.3, 1.0.2, etc.) - the blocklist is incomplete
-
Verify blocklist includes dangerous modulesInspect the source code or configuration where blocklist is defined; look for modules: uuid, _osx_support, _aix_support, _pyrepl.pager, imaplibAffected if any of these modules are missing from the blocklist - RCE via pickle is possible
-
Test with a benign pickle that imports dangerous moduleCreate a test pickle using the pickle module with: pickle.dumps({'import': 'uuid'}) and scan it with picklescan to see if import is blockedAffected if picklescan allows the import without warning - the blocklist is bypassed
If picklescan is installed with a version before 1.0.4 and the dangerous modules are not blocked, the environment is vulnerable to RCE through malicious pickle files.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpgrade to picklescan 1.0.4 or later which should include these dangerous modules in its blocklist. As a defense-in-depth measure, avoid loading pickle files from untrusted sources entirely and consider safer serialization formats like JSON.
1.0.4
- Verify the current installed version of picklescan by running: pip show picklescan
- Upgrade picklescan to version 1.0.4 or later by running: pip install picklescan>=1.0.4
- Verify the upgrade was successful by running: pip show picklescan and confirming the version is 1.0.4 or higher
- If using picklescan in automated scanning pipelines, verify that your integration still functions correctly with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56315 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56315 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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