Software weaknesses, explained simply
CWE names recurring weakness types found in software and devices; it is not a list of individual vulnerabilities. Scantide keeps the MITRE terminology visible, then explains what each weakness means and shows familiar, non-operational examples of what it can look like in a real product.
CWE-502 · Deserialization of Untrusted Data
Untrusted serialized data is reconstructed without adequate safeguards.
Headline signal
CWE-502 · Deserialization of Untrusted Data
Untrusted serialized data is reconstructed without adequate safeguards.
In plain English
Untrusted serialized data is reconstructed without adequate safeguards.
What this can look like
A service accepts a crafted serialized object that triggers unintended behavior while it is being reconstructed, potentially leading to code execution.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Examples are intentionally conceptual. They explain the security consequence without providing exploit payloads or step-by-step attack instructions. MITRE remains the authoritative source for the CWE definition and mapping guidance.