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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

2486 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)
Integrity Modify 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.
Availability DoS: 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.
Other Varies 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, Implementation If 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.
Implementation When 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.
Implementation Explicitly define a final object() to prevent deserialization.
Architecture and Design, Implementation Make 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.
Implementation Avoid 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 ID Title CVSS Severity Published
CVE-2026-62997 Kedro-Datasets: Remote code execution in experimental `PyTorchDataset` via unsafe `torch.load` — kedro-plugins 7.7 High 2026-09-16
CVE-2026-92785 Angel through 3.3.0 Unauthenticated Kryo Deserialization of Arbitrary Classes — angel 8.1 High 2026-09-16
CVE-2026-20340 Cisco Secure Firewall Management Center Software Deserialization Arbitrary Root Command Execution Vulnerability — Cisco Secure Firewall Management Center (FMC) 8.8 High 2026-09-16
CVE-2026-20242 Cisco Secure Firewall Management Center Software Java Deserialization Remote Code Execution Vulnerability — Cisco Secure Firewall Management Center (FMC) 9.8 Critical 2026-09-16
CVE-2026-20341 Cisco Secure Firewall Management Center Software sftunnel Deserialization Root Command Execution Vulnerability — Cisco Secure Firewall Management Center (FMC) 9.1 Critical 2026-09-16
CVE-2026-20211 Cisco Identity Services Engine Remote Code Execution Vulnerability — Cisco Identity Services Engine Software 9.1 Critical 2026-09-16
CVE-2026-20307 Cisco Identity Services Engine Remote Code Execution Vulnerability — Cisco Identity Services Engine Software 9.9 Critical 2026-09-16
CVE-2025-59953 LMdeploy has Remote Code Execution by Pickle Deserialization via zmq_rpc.call_and_response() in InterLM/lmdeploy — lmdeploy 9.8 Critical 2026-09-16
CVE-2026-70416 Dell ObjectScale 4.4.0前 不可信数据反序列化远程代码执行 — ObjectScale 10.0 Critical 2026-09-16
CVE-2026-91939 Cotonti 1.0.0 Comments Plugin PHP Object Injection via ci Parameter — Cotonti 9.8 Critical 2026-09-15
CVE-2026-11729 IBM MQ Java messaging is vulnerable to remote code execution — MQ 8.5 High 2026-09-15
CVE-2023-54398 Yonyou U8 Cloud Java Deserialization RCE via FileManageServlet — U8 Cloud 9.8 Critical 2026-09-15
CVE-2026-91842 OpenBankProject OBP-API Kryo Redis.scala KryoInjection.invert deserialization — OBP-API 4.1 Medium 2026-09-15
CVE-2026-46495 OpenDJ Pre-Auth RCE via Java Deserialization in JMX RMI — OpenDJ 9.2 Critical 2026-09-15
CVE-2026-45051 OpenAM Pre-auth RCE via Java Deserialization in WebAuthn Authenticator Storage — OpenAM 9.2 Critical 2026-09-15
CVE-2026-62263 OpenAM: WebAuthn Java deserialization RCE via ObjectInputFilter depth>1 bypass — OpenAM 9.2 Critical 2026-09-15
CVE-2026-45794 OpenAM Unsafe Java Deserialization via SNS — OpenAM 7.7 High 2026-09-15
CVE-2026-13293 IBM MQ Java messaging is vulnerable to remote code execution — MQ 8.8 High 2026-09-14
CVE-2026-67399 WHMCS 9.0.0-9.0.7/8.13.6及之前版本反序列化RCE — WHMCS 9.3 Critical 2026-09-14
CVE-2026-17156 IBM App Connect Enterprise Toolkit is vulnerable to arbitrary code execution due to multiple CVEs — App Connect Enterprise 7.8 High 2026-09-14
CVE-2026-17416 IBM App Connect Enterprise Toolkit is vulnerable to arbitrary code execution due to multiple CVEs — App Connect Enterprise 7.8 High 2026-09-14
CVE-2026-49400 October CMS: PHP Object Injection via Backend Widget Session Storage — october 3.3 Low 2026-09-14
CVE-2026-61701 Laravel MagicLink: Insecure Deserialization of MagicLink Actions Leads to Remote Code Execution — laravel-magiclink 8.8 High 2026-09-14
CVE-2026-90919 LightLLM through 1.2.0 Unauthenticated Remote Code Execution via Config Server Pickle Deserialization — LightLLM 9.8 Critical 2026-09-14
CVE-2026-90614 FedML-AI FedML MQTT+S3 Communication Backend remote_storage.py S3Storage.read_model deserialization — FedML 6.3 Medium 2026-09-14
CVE-2026-90575 PHPGurukul Small CRM Login Success login.php unserialize deserialization — Small CRM 3.7 Low 2026-09-13
CVE-2026-90777 ESPnet before 202609 Remote Code Execution via Unsafe Deserialization — espnet 8.8 High 2026-09-13
CVE-2026-90490 lenve vhr MailReceiver deserialization — vhr 6.3 Medium 2026-09-13
CVE-2026-78175 Tutor LMS <= 4.0.7 - Authenticated (Subscriber+) PHP Object Injection to Remote Code Execution — Tutor LMS – eLearning and online course solution 8.8 High 2026-09-12
CVE-2026-78006 The Events Calendar <= 6.17.4 - Unauthenticated PHP Object Injection to Remote Code Execution — The Events Calendar 9.8 Critical 2026-09-12

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