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-2026-23544 WordPress Valenti theme <= 5.6.3.5 - PHP Object Injection vulnerability — Valenti 8.8 High2026-02-19
CVE-2026-22333 WordPress YITH WooCommerce Compare plugin <= 3.6.0 - Deserialization of untrusted data vulnerability — YITH WooCommerce Compare 7.2 High2026-02-19
CVE-2025-15579 An Insecure Deserialization vulnerability has been discovered in OpenText™ Directory Services. — Directory Services 8.8AIHighAI2026-02-18
CVE-2026-1426 Advanced AJAX Product Filters <= 3.1.9.6 - Authenticated (Author+) PHP Object Injection via Live Composer Compatibility — Advanced AJAX Product Filters 8.8 High2026-02-18
CVE-2025-60038 Bosch Rexroth IndraWorks 安全漏洞 — IndraWorks 7.8 High2026-02-18
CVE-2025-60037 Bosch Rexroth IndraWorks 安全漏洞 — IndraWorks 7.8 High2026-02-18
CVE-2025-60036 Bosch Rexroth IndraWorks 安全漏洞 — IndraWorks 7.8 High2026-02-18
CVE-2025-60035 Bosch Rexroth IndraWorks 安全漏洞 — IndraWorks 7.8 High2026-02-18
CVE-2025-33253 NVIDIA Nemo Framework 代码问题漏洞 — NeMo Framework 7.8 High2026-02-18
CVE-2025-33252 NVIDIA Nemo Framework 代码问题漏洞 — NeMo Framework 7.8 High2026-02-18
CVE-2025-33245 NVIDIA Nemo Framework 代码问题漏洞 — NeMo Framework 8.0 High2026-02-18
CVE-2025-33243 NVIDIA Nemo Framework 代码问题漏洞 — NeMo Framework 7.8 High2026-02-18
CVE-2025-33241 NVIDIA Nemo Framework 代码问题漏洞 — NeMo Framework 7.8 High2026-02-18
CVE-2026-26220 LightLLM <= 1.1.0 PD Mode Unsafe Deserialization RCE — LightLLM 9.8AICriticalAI2026-02-17
CVE-2026-2555 JeecgBoot Retrieval-Augmented Generation AiragKnowledgeController.java importDocumentFromZip deserialization — JeecgBoot 5.0 Medium2026-02-16
CVE-2026-26208 ADB Explorer Vulnerable to Remote Code Execution via Insecure Deserialization — ADB-Explorer 7.8 High2026-02-13
CVE-2026-26221 Hyland OnBase Timer Services Unauthenticated .NET Remoting RCE — OnBase Workflow Timer Service 9.8 Critical2026-02-13
CVE-2026-26215 manga-image-translator Shared API Unsafe Deserialization RCE — manga-image-translator 9.8AICriticalAI2026-02-11
CVE-2026-0910 wpForo Forum <= 2.4.13 - Authenticated (Subscriber+) PHP Object Injection — wpForo Forum 8.8 High2026-02-11
CVE-2026-21511 Microsoft Outlook Spoofing Vulnerability — Microsoft 365 Apps for Enterprise 7.5 High2026-02-10
CVE-2026-21531 Azure SDK for Python Remote Code Execution Vulnerability — Azure AI Language Authoring 9.8 Critical2026-02-10
CVE-2026-23685 Insecure Deserialization vulnerability in SAP NetWeaver (JMS service) — SAP NetWeaver (JMS service) 4.4 Medium2026-02-10
CVE-2026-25925 PowerDocu Affected by Remote Code Execution via Insecure Deserialization — PowerDocu 7.8 High2026-02-09
CVE-2026-2113 yuan1994 tpadmin WebUploader preview.php deserialization — tpadmin 7.3 High2026-02-07
CVE-2026-25632 EPyT-Flow has unsafe JSON deserialization (__type__) — EPyT-Flow 10.0 Critical2026-02-06
CVE-2020-37071 CraftCMS 3 vCard Plugin 1.0.0 - Remote Code Execution — CraftCMS 9.8 Critical2026-02-03
CVE-2026-25615 Blesta 代码问题漏洞 — Blesta 7.2 High2026-02-03
CVE-2026-25614 Blesta 代码问题漏洞 — Blesta 7.5 High2026-02-03
CVE-2026-24954 WordPress WpEvently plugin <= 5.0.8 - Deserialization of untrusted data vulnerability — WpEvently 8.8 High2026-02-03
CVE-2026-1691 bolo-solo SnakeYAML BackupService.java importMarkdownsSync deserialization — bolo-solo 6.3 Medium2026-01-30

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