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

Goal: 1000 CNY · Raised: 1310 CNY

100%

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

1761 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-41699 Unsafe Deserialization in Spring GraphQL — Spring for GraphQL 8.1 High2026-06-11
CVE-2026-20251 Remote Code Execution through Deserialization of Untrusted Data in Splunk Secure Gateway — Splunk Enterprise 8.8 High2026-06-10
CVE-2026-52751 Ghidra < 12.1 - Remote Code Execution via Unfiltered RMI Deserialization in Shared Project Connection — ghidra 8.8 High2026-06-10
CVE-2026-10721 Concrete CMS below 9.5.2 is vulnerable to PHP Object Injection via unserialize() calls in the in Permission, Cache, and Search components — Concrete CMS--2026-06-10
CVE-2026-11815 Insecure Deserialization via MITM in Layer 7 Policy Manager — Layer 7 API Gateway--2026-06-10
CVE-2026-41732 In Spring for Apache Pulsar, overly broad trusted-package matching in header mapper exposes JDK classes to deserialization — Spring for Apache Pulsar 8.1 High2026-06-09
CVE-2026-41731 In Spring for Apache Kafka, overly broad trusted-package matching in header mappers exposes JDK classes to deserialization — Spring for Apache Kafka 8.1 High2026-06-09
CVE-2026-40993 Unfiltered Java Native Deserialization of SAML 2.0 Asserting Party Credentials BLOB Database Entry — Spring Security 7.3 High2026-06-09
CVE-2026-44963 Backup Server 域用户身份认证绕过导致远程代码执行 — Backup and Replication--2026-06-09
CVE-2026-48560 Microsoft SharePoint Server Spoofing Vulnerability — Microsoft SharePoint Enterprise Server 2016 5.4 Medium2026-06-09
CVE-2026-45484 Microsoft SharePoint Elevation of Privilege Vulnerability — Microsoft SharePoint Enterprise Server 2016 8.8 High2026-06-09
CVE-2026-26142 Nuance PowerScribe Remote Code Execution Vulnerability — Nuance PowerScribe 360 4.0 9.8 Critical2026-06-09
CVE-2026-49740 TYPO3 CMS - Insecure Deserialization in Core API — TYPO3 CMS--2026-06-09
CVE-2026-8365 Blocksy <= 2.1.41 - Authenticated (Contributor+) PHP Object Injection via Deserialization of Untrusted Data via 'blocksy_meta' REST API Field — Blocksy 8.8 High2026-06-09
CVE-2026-41855 Spring Framework Unsafe Deserialization via Jackson JMS Converters — Spring Framework 8.1 High2026-06-09
CVE-2026-7566 LearnPress – Backup & Migration Tool <= 4.1.4 - Authenticated (Administrator+) PHP Object Injection via WXR XML File Upload — LearnPress – Backup & Migration Tool 6.6 Medium2026-06-06
CVE-2026-7654 Admin Columns <= 7.0.18 - Authenticated (Contributor+) PHP Object Injection to Remote Code Execution via Custom Field Meta Value — Admin Columns 8.8 High2026-06-05
CVE-2026-25551 Seagull Software BarTender Deserialization Privilege Escalation via .NET Remoting Service — BarTender 2021 7.8 High2026-06-04
CVE-2026-50076 Apache Fory: Java ReplaceResolverSerializer deserialization checks bypass — Apache Fory--2026-06-04
CVE-2026-7888 Concrete CMS below 9.5.2 is vulnerable to PHP Object Injection via unserialize() calls in the Workflow, Form block, and File/Set components that lack the allowed_classes restriction. — Concrete CMS--2026-06-03
CVE-2026-47065 Apache MINA: Critical Deserialization Allow-list Bypass via resolveProxyClass - ZDRES-232 — Apache MINA 9.8 Critical2026-06-03
CVE-2026-34993 AIOHTTP Vulnerable to Deserialization of Untrusted Data — aiohttp 6.4 Medium2026-06-02
CVE-2026-42211 React Router's vendored turbo-stream v2 allows arbitrary constructor invocation via TYPE_ERROR deserialization leading to Unauth RCE — react-router 8.1 High2026-06-02
CVE-2026-24237 NVIDIA NVTabular反序列化漏洞 — NVTabular 7.8 High2026-06-02
CVE-2026-24221 NVIDIA NVTabular反序列化漏洞致代码执行 — NVTabular 7.8 High2026-06-02
CVE-2026-39555 WordPress Askka theme <= 1.3.1 - PHP Object Injection vulnerability — Askka 8.1 High2026-06-02
CVE-2026-39551 WordPress Töbel theme <= 1.8.1 - PHP Object Injection vulnerability — Töbel 8.1 High2026-06-02
CVE-2026-39550 WordPress Aperitif theme <= 1.6 - PHP Object Injection vulnerability — Aperitif 8.1 High2026-06-02
CVE-2026-10566 FoundationAgents MetaGPT schema.py Message.check_instruct_content deserialization — MetaGPT 5.3 Medium2026-06-02
CVE-2026-9330 IBM WebSphere Application Server is affected by remote code execution — WebSphere Application Server 8.5 High2026-06-01

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