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-65180 NVIDIA Megatron-LM 检查点加载 RCE 漏洞 — Megatron-LM 7.8 High 2026-10-13
CVE-2026-65110 NVIDIA Megatron-LM检查点加载远程代码执行漏洞 — Megatron-LM 7.8 High 2026-10-13
CVE-2026-108958 TensorLayer HDF5 Loading utils.py load_hdf5_graph deserialization — TensorLayer 6.3 Medium 2026-10-13
CVE-2026-108947 yoshitomo-matsubara torchdistill main_util.py load_ckpt deserialization — torchdistill 5.3 Medium 2026-10-13
CVE-2026-109361 MONAI 1.2.0 before 1.6.1 Insecure Deserialization RCE via nnUNetV2Runner postprocessing_file Path — MONAI 7.3 High 2026-10-12
CVE-2026-109360 MONAI 0.4.0 before 1.6.1 RCE via SENet Pretrained Weights Over Plaintext HTTP — MONAI 7.5 High 2026-10-12
CVE-2026-109237 Crawl4AI 0.9.0 before 0.9.4 Untrusted Config Gate Bypass Leaks Environment Variables — crawl4ai 8.1 High 2026-10-12
CVE-2026-109391 Square Squash through commit e73f280 Unauthenticated YAML Deserialization via Symbolication API — Squash 8.1 High 2026-10-12
CVE-2026-12613 Insecure Deserialization Leading to Remote Code Execution in Ministry of Justice's UYAP Document Editor — UYAP Document Editor 8.8 High 2026-10-12
CVE-2026-52903 YAML safe_load production fallback to unsafe_load enables RCE via deserialization — ManageIQ 8.8 High 2026-10-12
CVE-2026-81797 WordPress Buzz Stone | Magazine & Viral Blog WordPress Theme theme <= 1.0.2 - PHP Object Injection vulnerability — Buzz Stone | Magazine & Viral Blog WordPress Theme 9.8 Critical 2026-10-10
CVE-2026-78535 WordPress Photolia theme <= 1.0.3 - PHP Object Injection vulnerability — Photolia 9.8 Critical 2026-10-10
CVE-2026-78533 WordPress Qwery theme <= 3.6.1 - PHP Object Injection vulnerability — Qwery 9.8 Critical 2026-10-10
CVE-2026-78531 WordPress Jacqueline theme <= 2.22 - PHP Object Injection vulnerability — Jacqueline 9.8 Critical 2026-10-10
CVE-2026-78529 WordPress Alliance theme <= 3.11 - PHP Object Injection vulnerability — Alliance 9.8 Critical 2026-10-10
CVE-2026-66568 WordPress Original theme <= 1.9.0 - PHP Object Injection vulnerability — Original 9.8 Critical 2026-10-10
CVE-2026-66569 WordPress Kicker theme <= 2.2.1 - PHP Object Injection vulnerability — Kicker 9.8 Critical 2026-10-10
CVE-2026-66567 WordPress Anesta theme <= 1.5.3 - PHP Object Injection vulnerability — Anesta 9.8 Critical 2026-10-10
CVE-2026-66565 WordPress FC United theme <= 1.1.1 - PHP Object Injection vulnerability — FC United 9.8 Critical 2026-10-10
CVE-2026-66564 WordPress ShiftCV theme <= 3.0.14 - PHP Object Injection vulnerability — ShiftCV 9.8 Critical 2026-10-10
CVE-2026-66563 WordPress Windsor theme <= 2.10 - PHP Object Injection vulnerability — Windsor 9.8 Critical 2026-10-10
CVE-2026-66483 WordPress Education Center theme <= 3.6.12 - PHP Object Injection vulnerability — Education Center 9.8 Critical 2026-10-10
CVE-2026-66482 WordPress Drone Media theme <= 2.2.0 - PHP Object Injection vulnerability — Drone Media 9.8 Critical 2026-10-10
CVE-2026-62130 WordPress WooCommerce Multilingual & Multicurrency plugin <= 5.5.8 - PHP Object Injection vulnerability — WooCommerce Multilingual & Multicurrency 7.2 High 2026-10-10
CVE-2026-62125 WordPress Asia Garden theme <= 1.3.1 - PHP Object Injection vulnerability — Asia Garden 9.8 Critical 2026-10-10
CVE-2026-62124 WordPress N7 | Golf Club Sports & Events theme <= 2.21 - PHP Object Injection vulnerability — N7 | Golf Club Sports & Events 9.8 Critical 2026-10-10
CVE-2026-62123 WordPress Invetex theme <= 2.18 - PHP Object Injection vulnerability — Invetex 9.8 Critical 2026-10-10
CVE-2026-62120 WordPress Law Office theme <= 3.20 - PHP Object Injection vulnerability — Law Office 9.8 Critical 2026-10-10
CVE-2026-62090 WordPress WineShop theme <= 3.20 - PHP Object Injection vulnerability — WineShop 9.8 Critical 2026-10-10
CVE-2026-62087 WordPress Equadio theme <= 1.1.4 - PHP Object Injection vulnerability — Equadio 9.8 Critical 2026-10-10

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