How to fix: .NET BinaryFormatter Deserialization
The .NET BinaryFormatter class is instantiated or used to deserialize data.
Why it matters
BinaryFormatter deserializes untrusted data into arbitrary .NET types with no built-in type restriction, a pattern that has produced numerous public gadget-chain RCE exploits (e.g. via ysoserial.net).
Microsoft's own documentation states BinaryFormatter is 'insecure and cannot be made secure', and the type has been marked obsolete and is being removed from .NET entirely for this exact reason.
How to fix it
- 1Replace BinaryFormatter with a safe, schema-constrained serializer such as System.Text.Json or protobuf.
- 2If migration is not immediately possible, restrict BinaryFormatter to trusted, non-network-derived data only.
- 3Audit all deserialization entry points for the same underlying risk (NetDataContractSerializer, LosFormatter, SoapFormatter share similar issues).
Code examples
Use a safe serializer instead
// BAD
var formatter = new BinaryFormatter();
var obj = formatter.Deserialize(untrustedStream);
// GOOD
var obj = JsonSerializer.Deserialize<MyDto>(untrustedStream);References
Detected automatically by VulnRadar. The check id is code-deser-dotnet-binaryformatter, 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 .NET BinaryFormatter Deserialization?
- 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-dotnet-binaryformatter, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does .NET BinaryFormatter 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.