Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CWE-502 (可信数据的反序列化) — Vulnerability Class 1974

1974 vulnerabilities classified as CWE-502 (可信数据的反序列化). AI Chinese analysis included.

CWE-502 represents a critical security weakness where applications deserialize untrusted data without validating its integrity or structure. Attackers typically exploit this vulnerability by crafting malicious serialized objects that, when processed by the application, trigger unintended code execution or logic flaws. This often leads to remote code execution, denial of service, or privilege escalation, as the deserialization process may instantiate dangerous classes or invoke unsafe methods. To mitigate this risk, developers must strictly avoid deserializing data from untrusted sources. Instead, they should implement robust input validation, use allowlists for permitted data types, or adopt safer serialization formats like JSON that do not inherently support arbitrary object instantiation. Additionally, employing cryptographic signatures to verify data authenticity before deserialization ensures that only trusted, unaltered payloads are processed, effectively neutralizing the threat of malicious object injection.

MITRE CWE Description
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Common Consequences (3)
IntegrityModify Application Data, Unexpected State
Attackers can modify unexpected objects or data that was assumed to be safe from modification. Deserialized data or code could be modified without using the provided accessor functions, or unexpected functions could be invoked.
AvailabilityDoS: Resource Consumption (CPU)
If a function is making an assumption on when to terminate, based on a sentry in a string, it could easily never terminate.
OtherVaries by Context
The consequences can vary widely, because it depends on which objects or methods are being deserialized, and how they are used. Making an assumption that the code in the deserialized object is valid is dangerous and can enable exploitation. One example is attackers using gadget chains to perform una…
Mitigations (5)
Architecture and Design, ImplementationIf available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
ImplementationWhen deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
ImplementationExplicitly define a final object() to prevent deserialization.
Architecture and Design, ImplementationMake fields transient to protect them from deserialization. An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.
ImplementationAvoid having unnecessary types or gadgets (a sequence of instances and method invocations that can self-execute during the deserialization process, often found in libraries) available that can be leveraged for malicious ends. This limits the potential for unintended or unauthorized types and gadgets to be leveraged by the attacker. Add only acceptable classes to an allowlist. Note: new gadgets are…
Examples (2)
This code snippet deserializes an object from a file and uses it as a UI button:
try { File file = new File("object.obj"); ObjectInputStream in = new ObjectInputStream(new FileInputStream(file)); javax.swing.JButton button = (javax.swing.JButton) in.readObject(); in.close(); }
Bad · Java
private final void readObject(ObjectInputStream in) throws java.io.IOException { throw new java.io.IOException("Cannot be deserialized"); }
Good · Java
In Python, the Pickle library handles the serialization and deserialization processes. In this example derived from [REF-467], the code receives and parses data, and afterwards tries to authenticate a user based on validating a token.
try { class ExampleProtocol(protocol.Protocol): def dataReceived(self, data): # Code that would be here would parse the incoming data # After receiving headers, call confirmAuth() to authenticate def confirmAuth(self, headers): try: token = cPickle.loads(base64.b64decode(headers['AuthToken'])) if not check_hmac(token['signature'], token['data'], getSecretKey()): raise AuthFail self.secure_data = token['data'] except: raise AuthFail }
Bad · Python
CVE IDTitleCVSSSeverityPublished
CVE-2026-7871 Insecure Deserialization in Redis Cache Backend — Langflow OSS 9.8 Critical2026-06-30
CVE-2026-12578 DTMSoft - Deserialization of Untrusted Data Vulnerability — DTMSoft--2026-06-30
CVE-2026-12240 Export User Data <= 2.2.6 - Authenticated (Subscriber+) PHP Object Injection to Arbitrary File Deletion via display_name Field — Export User Data 8.0 High2026-06-30
CVE-2026-46386 OpenProject: Pre-authentication RCE in openproject/openproject Docker image via default `SECRET_KEY_BASE=OVERWRITE_ME` and `cookies_serializer = :marshal` — openproject 9.9 Critical2026-06-26
CVE-2026-56057 WordPress Uncanny Automator Pro plugin <= 7.3.0.6 - PHP Object Injection vulnerability — Uncanny Automator Pro 9.8 Critical2026-06-26
CVE-2026-56055 WordPress RealHomes theme <= 4.5.3 - PHP Object Injection vulnerability — RealHomes 8.8 High2026-06-26
CVE-2026-56032 WordPress Buddyboss Platform plugin <= 3.0.4 - PHP Object Injection vulnerability — Buddyboss Platform 9.8 Critical2026-06-26
CVE-2026-56031 WordPress Uncanny Automator plugin <= 7.3.1.2 - PHP Object Injection vulnerability — Uncanny Automator 8.1 High2026-06-26
CVE-2026-57527 ZAP ViewState Add-on Insecure Deserialization via JSFViewState.decode() — zap-extensions 8.8 High2026-06-26
CVE-2026-53914 JetBrains Kotlin 反序列化注入漏洞 — Kotlin 6.7 Medium2026-06-26
CVE-2025-71340 picklescan - Remote Code Execution via idlelib.pyshell.ModifiedInterpreter.runcode — picklescan 8.1 High2026-06-25
CVE-2026-46607 Glances: Insecure Pickle Deserialization in Version Cache Leads to Arbitrary Code Execution — glances 7.8 High2026-06-25
CVE-2026-56053 WordPress EventPrime plugin <= 4.3.4.1 - PHP Object Injection vulnerability — EventPrime 8.8 High2026-06-25
CVE-2026-10043 MosaicML Composer Deserialization of Untrusted Data Remote Code Execution Vulnerability — Composer--2026-06-24
CVE-2026-56121 Feast < 0.63.0 Unauthenticated RCE via ApplyFeatureView gRPC Deserialization — feast 9.8 Critical2026-06-24
CVE-2025-71354 picklescan - Remote Code Execution via idlelib.debugobj.ObjectTreeItem.SetText — picklescan 8.1 High2026-06-24
CVE-2026-41862 Spring Statemachine 反序列化注入漏洞 — Spring Statemachine 8.8 High2026-06-23
CVE-2025-71376 picklescan - Arbitrary Code Execution via Undetected idlelib.autocomplete.AutoComplete.fetch_completions — picklescan 8.1 High2026-06-23
CVE-2025-71370 picklescan - Remote Code Execution via torch.jit.unsupported_tensor_ops.execWrapper — picklescan 8.1 High2026-06-23
CVE-2025-71365 picklescan - Arbitrary Code Execution via numpy.f2py.crackfortran.myeval Detection Bypass — picklescan 8.1 High2026-06-23
CVE-2025-71341 picklescan - Remote Code Execution via Undetected profile.Profile.runctx — picklescan 8.1 High2026-06-23
CVE-2025-71358 picklescan - Remote Code Execution via idlelib.autocomplete.AutoComplete.get_entity — picklescan 8.1 High2026-06-22
CVE-2025-71344 picklescan - Arbitrary Code Execution via Undetected ensurepip._run_pip Function — picklescan 8.1 High2026-06-22
CVE-2025-71339 Picklescan - Arbitrary Code Execution via numpy.f2py.crackfortran._eval_length Gadget — Picklescan 8.1 High2026-06-22
CVE-2026-45034 PhpSpreadsheet: File::prohibitWrappers bypass — PhpSpreadsheet--2026-06-22
CVE-2025-71378 picklescan - Remote Code Execution via Undetected cProfile.runctx in Pickle Files — picklescan 8.1 High2026-06-21
CVE-2025-71357 picklescan - Arbitrary Code Execution via Undetected idlelib.pyshell.ModifiedInterpreter.runcommand — picklescan 8.1 High2026-06-21
CVE-2025-71348 picklescan - Arbitrary Code Execution via torch.utils._config_module.load_config Bypass — picklescan 8.1 High2026-06-21
CVE-2026-12787 zhilink 智互联(深圳)科技有限公司 ADP Application Developer Platform 应用开发者平台 testConnection Endpoint deserialization — ADP Application Developer Platform 应用开发者平台 6.3 Medium2026-06-21
CVE-2026-56304 picklescan - Arbitrary File Creation via logging.FileHandler Deserialization — picklescan 6.5 Medium2026-06-20

Vulnerabilities classified as CWE-502 (可信数据的反序列化) represent 1974 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.