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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

1687 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-2025-60237 WordPress Finag theme <= 1.5.0 - PHP Object Injection vulnerability — Finag 9.8 Critical2026-03-19
CVE-2025-60233 WordPress Zuut theme <= 1.4.2 - PHP Object Injection vulnerability — Zuut 9.8 Critical2026-03-19
CVE-2026-27096 WordPress ColorFolio - Freelance Designer WordPress Theme theme <= 1.3 - Deserialization of untrusted data vulnerability — ColorFolio - Freelance Designer WordPress Theme 8.1 High2026-03-19
CVE-2026-25873 OmniGen2-RL Reward Server Unsafe Deserialization RCE — OmniGen2-RL 9.8 Critical2026-03-18
CVE-2026-25449 WordPress Traveler theme < 3.2.8.1 - PHP Object Injection vulnerability — Traveler 9.8 Critical2026-03-18
CVE-2026-25769 Wazuh Cluster vulnerable to Remote Code Execution via Insecure Deserialization — wazuh 9.1 Critical2026-03-17
CVE-2026-1323 Insecure Deserialization in extension "Mailqueue" (mailqueue) — Extension "Mailqueue" 8.8AIHighAI2026-03-17
CVE-2025-54920 Apache Spark: Spark History Server Code Execution Vulnerability — Apache Spark 8.8 -2026-03-14
CVE-2026-32355 WordPress JetEngine plugin < 3.8.4.1 - Deserialization of untrusted data vulnerability — JetEngine 8.8 High2026-03-13
CVE-2025-13913 Inductive Automation Ignition Software Deserialization of Untrusted Data — Ignition Software 6.3 Medium2026-03-12
CVE-2026-3967 Alfresco Activiti Process Variable Serialization System SerializableType.java createObjectInputStream deserialization — Activiti 6.3 Medium2026-03-12
CVE-2026-22248 GLPI affected by Remote Code Execution via malicious upload — glpi 8.1 High2026-03-11
CVE-2026-1286 Schneider Electric EcoStruxure Foxboro DCS 代码问题漏洞 — EcoStruxure™ Foxboro DCS 7.8AIHighAI2026-03-10
CVE-2026-26114 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 8.8 High2026-03-10
CVE-2026-25166 Windows System Image Manager Assessment and Deployment Kit (ADK) Remote Code Execution Vulnerability — Windows ADK for Windows 10, version 2004 7.8 High2026-03-10
CVE-2025-11739 Schneider Electric EcoStruxure Power Monitoring Expert和Schneider Electric EcoStruxure Power Operation(Schneider Electric EPO) 代码问题漏洞 — EcoStruxure™ Power Monitoring Expert (PME) 7.8AIHighAI2026-03-10
CVE-2026-27685 Insecure Deserialization in SAP NetWeaver Enterprise Portal Administration — SAP NetWeaver Enterprise Portal Administration 9.1 Critical2026-03-10
CVE-2026-2020 JS Archive List <= 6.1.7 - Authenticated (Contributor+) PHP Object Injection via 'included' Shortcode Attribute — JS Archive List 7.5 High2026-03-07
CVE-2026-28277 LangGraph: Unsafe msgpack deserialization in LangGraph checkpoint loading — langgraph 6.8 Medium2026-03-05
CVE-2026-27749 Avira Internet Security System Speedup Insecure Deserialization — Avira Internet Security 7.8 High2026-03-05
CVE-2026-2599 Database for Contact Form 7, WPforms, Elementor forms <= 1.4.7 - Unauthenticated PHP Object Injection via 'download_csv' — Database for Contact Form 7, WPforms, Elementor forms 9.8 Critical2026-03-05
CVE-2026-28105 WordPress Good Energy theme <= 1.7.7 - PHP Object Injection vulnerability — Good Energy 9.8 Critical2026-03-05
CVE-2026-28074 WordPress Pizza House theme <= 1.4.0 - PHP Object Injection vulnerability — Pizza House 9.8 Critical2026-03-05
CVE-2026-27439 WordPress Dentario theme <= 1.5 - PHP Object Injection vulnerability — Dentario 9.8 Critical2026-03-05
CVE-2026-27417 WordPress Sweet Date theme < 4.0.1 - PHP Object Injection vulnerability — Sweet Date 9.8 Critical2026-03-05
CVE-2026-27437 WordPress Tennis Club theme <= 1.2.3 - PHP Object Injection vulnerability — Tennis Club 9.8 Critical2026-03-05
CVE-2026-27438 WordPress Kingler theme <= 1.7 - PHP Object Injection vulnerability — Kingler 9.8 Critical2026-03-05
CVE-2026-27379 WordPress NextScripts plugin <= 4.4.7 - PHP Object Injection vulnerability — NextScripts 8.8 High2026-03-05
CVE-2026-27369 WordPress Celeste theme <= 1.3.6 - PHP Object Injection vulnerability — Celeste 8.1 High2026-03-05
CVE-2026-27338 WordPress Car Zone theme <= 3.7 - Deserialization of untrusted data vulnerability — Car Zone 8.8 High2026-03-05

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