How to fix: Potential Insecure Deserialization
Deserialization operations on potentially untrusted data.
Why it matters
Insecure deserialization can allow remote code execution.
Deserializing untrusted data can instantiate arbitrary objects or execute code.
How to fix it
- 1Only deserialize data from trusted sources.
- 2Use safe formats like JSON.
- 3Implement integrity checks (signatures/HMACs).
- 4Use allowlists for deserializable classes.
Code examples
Safe JSON parsing
const schema = z.object({ id: z.number(), name: z.string() });
const data = schema.parse(JSON.parse(input));References
Detected automatically by VulnRadar. The check id is insecure-deserialization, 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
- Mediumeval() Usage in Inline Scripts
- MediuminnerHTML DOM XSS Sink
Questions
- How severe is Potential Insecure Deserialization?
- VulnRadar rates this high 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 insecure-deserialization, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Potential Insecure Deserialization 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.