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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

2492 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-2025-71367 picklescan - Remote Code Execution via _operator.attrgetter Detection Bypass — picklescan 8.1 High 2026-07-04
CVE-2025-71364 picklescan - Arbitrary Code Execution via Undetected asyncio.unix_events._UnixSubprocessTransport._start — picklescan 8.1 High 2026-07-04
CVE-2025-71360 picklescan - Remote Code Execution via Undetected idlelib.calltip.get_entity — picklescan 8.1 High 2026-07-04
CVE-2025-71362 picklescan - Arbitrary Code Execution via Unsafe Deserialization in numpy.f2py.crackfortran — picklescan 8.1 High 2026-07-04
CVE-2025-71359 picklescan - Unsafe Deserialization via lib2to3.pgen2.grammar.Grammar.loads — picklescan 8.1 High 2026-07-04
CVE-2025-71356 picklescan - Arbitrary Code Execution via torch.fx.experimental.symbolic_shapes.ShapeEnv.evaluate_guards_expression — picklescan 8.1 High 2026-07-04
CVE-2025-71353 picklescan - Remote Code Execution via torch._dynamo.guards.GuardBuilder.get — picklescan 8.1 High 2026-07-04
CVE-2025-71347 picklescan - Undetected Remote Code Execution via numpy.f2py.crackfortran.param_eval — picklescan 8.1 High 2026-07-04
CVE-2025-71345 picklescan - Arbitrary Code Execution via torch.utils.bottleneck.__main__.run_autograd_prof — picklescan 8.1 High 2026-07-04
CVE-2025-71343 picklescan - Arbitrary Code Execution via lib2to3.pgen2.pgen.ParserGenerator.make_label Detection Bypass — picklescan 8.1 High 2026-07-04
CVE-2025-71342 picklescan - Undetected Remote Code Execution via idlelib.run.Executive.runcode — picklescan 8.1 High 2026-07-04
CVE-2026-12481 Deserialization of Untrusted Data in keras-team/keras — keras-team/keras - - 2026-07-03
CVE-2026-13371 WatchGuard Firebox Management Web UI Denial of Service via Unsafe Deserialization — Fireware OS 6.9 Medium 2026-07-02
CVE-2026-56037 WordPress Themify Popup plugin <= 1.4.3 - PHP Object Injection vulnerability — Themify Popup 8.8 High 2026-07-02
CVE-2026-57677 WordPress Novalnet Payment Gateway for WooCommerce plugin <= 12.10.3 - PHP Object Injection vulnerability — Novalnet Payment Gateway for WooCommerce 9.8 Critical 2026-07-02
CVE-2026-57621 WordPress Booktics plugin <= 1.0.21 - PHP Object Injection vulnerability — Booktics 9.8 Critical 2026-07-02
CVE-2026-27414 WordPress Werkstatt theme <= 4.8.3 - PHP Object Injection vulnerability — Werkstatt 8.8 High 2026-07-02
CVE-2026-27060 WordPress ARMember Premium plugin < 7.6 - PHP Object Injection vulnerability — ARMember Premium 8.8 High 2026-07-02
CVE-2026-55153 mchange-commons-java contains elements susceptible to abuse via JNDI injection and "deserialization gadgets" — mchange-commons-java 7.1 High 2026-07-01
CVE-2026-14265 RCE via Deserialization in AWS Advanced JDBC Wrapper — AWS Advanced JDBC Wrapper 7.5 High 2026-07-01
CVE-2026-57516 Ray < 2.56.0 Unsafe Deserialization RCE via WebDataset Reader — Ray 8.8 High 2026-07-01
CVE-2026-58025 Remote Code Execution via Unsafe Deserialization in LogItem Import — MediaWiki - - 2026-07-01
CVE-2026-24251 NVIDIA Megatron Bridge 反序列化注入漏洞 — Megatron-Bridge 7.8 High 2026-07-01
CVE-2026-24250 NVIDIA Megatron Bridge 反序列化注入漏洞 — Megatron-Bridge 7.8 High 2026-07-01
CVE-2026-24247 NVIDIA Megatron Bridge 反序列化注入漏洞 — Megatron-Bridge 7.8 High 2026-07-01
CVE-2026-24245 NVIDIA Megatron Bridge 反序列化注入漏洞 — Megatron-Bridge 7.8 High 2026-07-01
CVE-2026-24244 NVIDIA Megatron Bridge 反序列化注入漏洞 — Megatron-Bridge 7.8 High 2026-07-01
CVE-2026-24243 NVIDIA Megatron Bridge 反序列化注入漏洞 — Megatron-Bridge 7.8 High 2026-07-01
CVE-2026-24240 NVIDIA Megatron Bridge 反序列化注入漏洞 — Megatron-Bridge 7.8 High 2026-07-01
CVE-2026-10538 Improper deserialization handling in Control-M Components — Control-M/Enterprise Manager 8.0 High 2026-07-01

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