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-40901 DataEase: Quartz Deserialization → Remote Code Execution — dataease 8.8AIHighAI2026-04-16
CVE-2025-15610 OpenText RightFax 安全漏洞 — RightFax 9.8 -2026-04-15
CVE-2026-27303 Adobe Connect | Deserialization of Untrusted Data (CWE-502) — Adobe Connect 9.6 Critical2026-04-14
CVE-2026-34615 Adobe Connect | Deserialization of Untrusted Data (CWE-502) — Adobe Connect 9.3 Critical2026-04-14
CVE-2026-32192 Azure Monitor Agent Elevation of Privilege Vulnerability — Azure Monitor 7.8 High2026-04-14
CVE-2026-32184 Microsoft High Performance Compute (HPC) Pack Elevation of Privilege Vulnerability — Microsoft HPC Pack 2019 7.8 High2026-04-14
CVE-2026-3017 Smart Post Show – Post Grid, Post Carousel & Slider, and List Category Posts <= 3.0.12 - Authenticated (Administrator+) PHP Object Injection — Smart Post Show – Post Grid, Post Carousel & Slider, and List Category Posts 7.2 High2026-04-14
CVE-2026-40044 Pachno 1.0.6 FileCache Deserialization Remote Code Execution — Pachno 9.8 Critical2026-04-13
CVE-2026-1462 Safe Mode Bypass in keras-team/keras — keras-team/keras 7.5 -2026-04-13
CVE-2026-33858 Apache Airflow: Unsafe Deserialization via Legacy Serialization Keys (__type/__var) Bypass in XCom API — Apache Airflow 9.8 -2026-04-13
CVE-2026-35337 Apache Storm Client: RCE through Unsafe Deserialization via Kerberos TGT Credential Handling — Apache Storm Client 8.8 -2026-04-13
CVE-2026-25204 SAMSUNG Escargot 安全漏洞 — Escargot 6.2 Medium2026-04-13
CVE-2026-5507 Session Cache Restore — Arbitrary Free via Deserialized Pointer — wolfSSL 8.1AIHighAI2026-04-09
CVE-2026-3199 Nexus Repository 3 - Authenticated Remote Code Execution via Task Property Injection — Nexus Repository 7.2AIHighAI2026-04-08
CVE-2026-39890 PraisonAI Affected by Remote Code Execution via YAML Deserialization in Agent Definition Loading — PraisonAI 9.8 Critical2026-04-08
CVE-2026-32590 Mirror-registry: remote code execution using pickle deserialization — mirror registry for Red Hat OpenShift 7.1 High2026-04-08
CVE-2026-3296 Everest Forms <= 3.4.3 - Unauthenticated PHP Object Injection via Form Entry Metadata — Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder 9.8 Critical2026-04-08
CVE-2026-3357 IBM Langflow Desktop FAISS Vector Store Remote Code Execution via malicious Pickle file — Langflow Desktop 8.8 High2026-04-08
CVE-2026-33439 Pre-Authentication Remote Code Execution via `jato.clientSession` Deserialization in OpenAM — OpenAM 9.8AICriticalAI2026-04-07
CVE-2026-24156 NVIDIA DALI 代码问题漏洞 — DALI 7.3 High2026-04-07
CVE-2026-35464 pyLoad has an incomplete fix for CVE-2026-33509: unprotected storage_folder enables arbitrary file write to Flask session store and code execution — pyload 7.5 High2026-04-07
CVE-2026-1839 Arbitrary Code Execution via Unsafe torch.load() in Trainer Checkpoint Loading in huggingface/transformers — huggingface/transformers 9.8AICriticalAI2026-04-07
CVE-2026-5659 pytries datrie trie File datrie.pyx Trie.__setstate__ deserialization — datrie 6.3 Medium2026-04-06
CVE-2026-5536 FedML-AI FedML gRPC server grpc_server.py sendMessage deserialization — FedML 7.3 High2026-04-05
CVE-2026-5473 NASA cFS Pickle pickle.load deserialization — cFS 4.5 Medium2026-04-03
CVE-2026-35537 Roundcube Webmail 代码问题漏洞 — Webmail 3.7 Low2026-04-03
CVE-2026-34838 Group-Office: Authenticated Remote Code Execution via PHP Insecure Deserialization in `AbstractSettingsCollection` — groupoffice 10.0 Critical2026-04-02
CVE-2026-29782 OpenSTAManager: Remote Code Execution via Insecure Deserialization in OAuth2 — openstamanager 7.2 High2026-04-02
CVE-2026-24165 NVIDIA BioNeMo 代码问题漏洞 — BioNeMo Framework 7.8 High2026-03-31
CVE-2026-24164 NVIDIA BioNeMo 代码问题漏洞 — BioNeMo Framework 8.8 High2026-03-31

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