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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

2488 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-64901 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 8.8 High 2026-08-11
CVE-2026-70321 Microsoft SharePoint Remote Code Execution Vulnerability — Microsoft SharePoint Server Subscription Edition 8.8 High 2026-08-11
CVE-2026-65815 Microsoft Dynamics 365 On-Premises Remote Code Execution Vulnerability — Microsoft Dynamics 365 (on-premises) version 9.1 8.8 High 2026-08-11
CVE-2026-65665 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Server 2019 8.8 High 2026-08-11
CVE-2026-65663 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 8.8 High 2026-08-11
CVE-2026-65658 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 8.8 High 2026-08-11
CVE-2026-62912 Microsoft Exchange Server Denial of Service Vulnerability — Microsoft Exchange Server 2016 Cumulative Update 23 6.5 Medium 2026-08-11
CVE-2026-59124 Microsoft High Performance Computing (HPC) Pack Remote Code Execution Vulnerability — Microsoft HPC Pack 2019 9.8 Critical 2026-08-11
CVE-2026-63516 Microsoft SharePoint Server Spoofing Vulnerability — Microsoft SharePoint Enterprise Server 2016 6.5 Medium 2026-08-11
CVE-2026-63514 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 8.8 High 2026-08-11
CVE-2026-17061 Deserialization of Untrusted Data Vulnerability in SIMULIA Execution Engine from Release 2023 through Release 2026 — SIMULIA Execution Engine 10.0 Critical 2026-08-11
CVE-2026-15555 Jboss-marshalling-river: wildfly-clustering-infinispan-marshalling: jboss deserialization rce via unfiltered river unmarshaller — Red Hat JBoss Enterprise Application Platform 7.4.25 8.8 High 2026-08-11
CVE-2026-18948 Feast: feast: unsafe dill deserialization of registry-stored udfs — rce on feature server and registry server — Red Hat OpenShift AI 2.25 9.9 Critical 2026-08-10
CVE-2026-69659 Memory exhaustion via unbounded deserialization of keyset pagination cursors in Ash.Page.Keyset — ash 5.9 Medium 2026-08-09
CVE-2026-68772 ZenML 0.94.6 Remote Code Execution via CloudpickleMaterializer — ZenML 8.0 High 2026-08-07
CVE-2026-71559 Apache Fory: Uncaught panic (remote DoS) in Go meta-string decoder from untrusted metadata — Apache Fory - - 2026-08-07
CVE-2026-71558 Apache Fory: Heap type confusion in C++ polymorphic smart-pointer deserialization — Apache Fory - - 2026-08-07
CVE-2026-71560 Apache Fory: Out-of-bounds heap read in C++ struct deserializer tagged-int fast-path — Apache Fory - - 2026-08-07
CVE-2026-50515 Azure Service Bus Remote Code Execution Vulnerability — Azure Service Bus 9.9 Critical 2026-08-06
CVE-2026-65581 WordPress AI ANN theme <= 1.29.0 - PHP Object Injection vulnerability — AI ANN 9.8 Critical 2026-08-06
CVE-2026-65579 WordPress Agricola theme <= 1.21.0 - PHP Object Injection vulnerability — Agricola 9.8 Critical 2026-08-06
CVE-2026-65578 WordPress Agora theme <= 1.9 - PHP Object Injection vulnerability — Agora 9.8 Critical 2026-08-06
CVE-2026-65577 WordPress Advice theme <= 1.18.0 - PHP Object Injection vulnerability — Advice 9.8 Critical 2026-08-06
CVE-2026-65576 WordPress Adrena theme <= 1.2.14 - PHP Object Injection vulnerability — Adrena 9.8 Critical 2026-08-06
CVE-2026-65575 WordPress Accalia theme <= 1.5.3 - PHP Object Injection vulnerability — Accalia 9.8 Critical 2026-08-06
CVE-2026-65574 WordPress Abogado theme <= 1.18 - PHP Object Injection vulnerability — Abogado 9.8 Critical 2026-08-06
CVE-2026-65573 WordPress Abelle theme <= 1.22 - PHP Object Injection vulnerability — Abelle 9.8 Critical 2026-08-06
CVE-2026-65571 WordPress 69 Clothing theme <= 1.2.11.1 - PHP Object Injection vulnerability — 69 Clothing 9.8 Critical 2026-08-06
CVE-2026-65572 WordPress A.Williams theme <= 1.3.1 - PHP Object Injection vulnerability — A.Williams 9.8 Critical 2026-08-06
CVE-2026-65556 WordPress WPBruiser {no- Captcha anti-Spam} plugin <= 3.1.43 - PHP Object Injection vulnerability — WPBruiser {no- Captcha anti-Spam} 9.8 Critical 2026-08-06

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