How to fix: pickle.loads on untrusted bytes
pickle.loads(untrusted_bytes) reconstructs arbitrary Python objects and executes their __reduce__ method. Crafted pickles achieve arbitrary code execution at parse time.
Why it matters
Untrusted pickle data triggers arbitrary code execution in the Python interpreter.
The `code-deser-pickle-loads` check verifies that the server does not expose the `deser-pickle-loads` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.
How to fix it
- 1Never unpickle data from untrusted sources; use JSON or msgpack instead.
- 2If unavoidable, verify an HMAC signature on the pickled bytes before loading.
- 3Use pickle.loads only in isolated processes with restricted privileges.
Code examples
Never unpickle data from untrusted sources
# BAD: pickle.loads executes arbitrary Python code
import pickle
data = pickle.loads(user_input)
# GOOD: use JSON or a safe format for untrusted data
import json
data = json.loads(user_input)
# Validate with a schema (e.g., pydantic):
from pydantic import BaseModel
class Payload(BaseModel):
name: str
value: int
payload = Payload(**data)References
Detected automatically by VulnRadar. The check id is code-deser-pickle-loads, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is pickle.loads on untrusted bytes?
- VulnRadar rates this critical severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id code-deser-pickle-loads, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does pickle.loads on untrusted bytes map to?
- It maps to CWE-502. In the OWASP Top 10 it falls under A08:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.