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-96344 WordPress eCommerce Product Catalog plugin <= 3.6.0 - PHP Object Injection vulnerability — eCommerce Product Catalog 7.2 High 2026-09-30
CVE-2026-96343 WordPress WP ERP plugin <= 1.17.9 - PHP Object Injection vulnerability — WP ERP 7.2 High 2026-09-30
CVE-2026-95531 WordPress Conversational Forms for ChatBot plugin <= 1.5.0 - PHP Object Injection vulnerability — Conversational Forms for ChatBot 8.8 High 2026-09-30
CVE-2026-94683 WordPress DesignSetGo plugin <= 2.8.0 - PHP Object Injection vulnerability — DesignSetGo 8.8 High 2026-09-30
CVE-2026-94678 WordPress Go Live Update Urls plugin <= 7.0.8 - PHP Object Injection vulnerability — Go Live Update Urls 8.8 High 2026-09-30
CVE-2026-94677 WordPress Kadence WooCommerce Email Designer plugin <= 1.5.19.1 - PHP Object Injection vulnerability — Kadence WooCommerce Email Designer 7.2 High 2026-09-30
CVE-2026-94122 WordPress Responsive Slider Gallery plugin <= 1.5.5 - PHP Object Injection vulnerability — Responsive Slider Gallery 7.2 High 2026-09-30
CVE-2026-94121 WordPress 10Web Booster – Website speed optimization, Cache & Page Speed optimizer plugin <= 2.33.6 - PHP Object Injection vulnerability — 10Web Booster – Website speed optimization, Cache & Page Speed optimizer 8.8 High 2026-09-30
CVE-2026-94076 WordPress SEO Plugin by Squirrly SEO plugin <= 14.2.5 - PHP Object Injection vulnerability — SEO Plugin by Squirrly SEO 8.8 High 2026-09-30
CVE-2026-93771 WordPress Cost of Goods for WooCommerce plugin <= 3.5.2 - PHP Object Injection vulnerability — Cost of Goods for WooCommerce 7.2 High 2026-09-30
CVE-2026-93651 WordPress Minimum and Maximum Quantity for WooCommerce plugin <= 2.1.2 - PHP Object Injection vulnerability — Minimum and Maximum Quantity for WooCommerce 7.2 High 2026-09-30
CVE-2026-93624 WordPress Music Player for WooCommerce plugin <= 1.9.1 - PHP Object Injection vulnerability — Music Player for WooCommerce 7.2 High 2026-09-30
CVE-2026-102455 DigiWin|EasyFlow .NET - Insecure Deserialization — EasyFlow .NET 9.8 Critical 2026-09-30
CVE-2026-13046 Fireware OS Deserialization of Untrusted Data in samld Allows Remote Code Execution — Fireware OS 7.5 High 2026-09-29
CVE-2026-103041 LightLLM through 1.2.0 Unauthenticated Remote Code Execution via Embed Cache RPyC Service — LightLLM 9.8 Critical 2026-09-29
CVE-2026-103040 LightLLM through 1.2.0 Unauthenticated Remote Code Execution via Router Profiler RPyC Service — LightLLM 9.8 Critical 2026-09-29
CVE-2026-100308 GluonTS arbitrary command execution during model deserialization — gluonts 7.8 High 2026-09-29
CVE-2026-101169 Octopus Server 反序列化漏洞可致任意代码执行 — Octopus Server 8.7 High 2026-09-29
CVE-2026-81867 Deserialization of Untrusted Data in Application Integration allows Remote Code Execution — Application Integration 9.4 Critical 2026-09-28
CVE-2026-82384 Apache Roller: Unauthenticated deserialization in the XML-RPC endpoint — Apache Roller 9.8 Critical 2026-09-28
CVE-2026-100846 MONAI before 1.5.2 Remote Code Execution via Pickle Deserialization — MONAI 7.6 High 2026-09-27
CVE-2026-100845 MONAI before 1.6.0 Remote Code Execution via NumpyReader — MONAI 7.8 High 2026-09-27
CVE-2026-100843 MONAI before 1.6.0 Remote Code Execution via algo_from_pickle — MONAI 7.8 High 2026-09-27
CVE-2026-100841 MONAI through 1.6.0 PersistentDataset Remote Code Execution via Pickle Cache — MONAI 7.8 High 2026-09-27
CVE-2026-97869 langchain4j LangChain4j-agentic AgenticScopeJsonSerializationIT.java AgenticScopeSerializer.fromJson deserialization — langchain4j 4.1 Medium 2026-09-25
CVE-2026-84862 IBM Guardium Data Protection is affected by multiple vulnerabilities. — Guardium Data Protection 7.2 High 2026-09-25
CVE-2026-97865 Open-Web-Analytics Remote Event Queue Endpoint queue.php loadFromArray deserialization — Open-Web-Analytics 7.3 High 2026-09-25
CVE-2026-96745 PHP object injection via unsuppressible __pclass class inference in command monitoring events — PHP Driver 5.6 Medium 2026-09-24
CVE-2026-63630 BentoPDF: Workflow Import Allows Unvalidated TSA URL Leading to PDF Hash Exfiltration via RFC 3161 Requests — bentopdf 3.4 Low 2026-09-24
CVE-2026-82093 DataStage on Cloud Pak for Data has several vulnerabilities — DataStage on Cloud Pak for Data 8.8 High 2026-09-24

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