PatchSiren cyber security CVE debrief
CVE-2026-53872 picklescan CVE debrief
CVE-2026-53872 is a HIGH-severity vulnerability in picklescan, a software that was vulnerable to unsafe pickle deserialization. This vulnerability, with a CVSS score of 8.7, allowed unauthenticated attackers to read arbitrary server files by chaining io.FileIO and urllib.request.urlopen. Attackers could bypass RCE-focused blocklists to exfiltrate sensitive data like /etc/passwd to external servers. The vulnerability was published on June 17, 2026, and immediately modified the same day. Users of picklescan should take immediate action to protect their systems.
- Vendor
- picklescan
- Product
- Unknown
- CVSS
- HIGH 8.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-06-17
- Original CVE updated
- 2026-06-17
- Advisory published
- 2026-06-17
- Advisory updated
- 2026-06-17
Who should care
Users of picklescan, especially those using versions before 0.0.35, should be aware of this vulnerability and take immediate action to protect their systems. Security teams and administrators responsible for servers with picklescan installed should prioritize patching and mitigation.
Technical summary
The vulnerability in picklescan arises from unsafe pickle deserialization. Pickle is a Python module for serializing and de-serializing Python objects. When picklescan deserializes untrusted input, it can lead to arbitrary code execution or, in this case, reading of arbitrary files. The exploit involves chaining io.FileIO and urllib.request.urlopen to read server files. This vulnerability has been assigned CWE-22, indicating it involves improper limitation of a pathname to a restricted directory.
Defensive priority
HIGH
Recommended defensive actions
- Update picklescan to version 0.0.35 or later.
- Restrict access to picklescan to only trusted users and networks.
- Implement additional security measures such as Web Application Firewalls (WAFs) to detect and prevent exploitation attempts.
- Monitor systems for suspicious activity that could indicate exploitation.
- Consider replacing picklescan with a safer alternative if available.
- Regularly review and update software dependencies to ensure they are secure.
- Limit the use of pickle for deserialization of untrusted input.
Evidence notes
The information provided is based on data from the National Vulnerability Database (NVD) and other reliable sources. The CVE record and NVD detail pages provide comprehensive information about the vulnerability, including its CVSS score, vector, and references.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-53872 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-53872
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-53872 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-53872
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/mmaitre314/picklescan/security/advisories/GHSA-9726-w42j-3qjr
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/picklescan-arbitrary-file-read-via-unsafe-pickle-deserialization
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.