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-1928 Rank Math SEO <= 1.0.276 - Authenticated (Contributor+) PHP Object Injection to Remote Code Execution — Rank Math SEO – AI SEO Tools to Dominate SEO Rankings 8.8 High 2026-10-28
CVE-2026-110879 jackson-databind: PolymorphicTypeValidator bypass via generic type arguments and array element types allows arbitrary class instantiation (incomplete fix for CVE-2026-54512) — jackson-databind 9.8 Critical 2026-10-28
CVE-2026-75891 Kirki <= 6.2.5 - Authenticated (Subscriber+) PHP Object Injection to Administrator Account Takeover via 'get-single-symbol' AJAX Endpoint — Kirki – Freeform Page Builder, Website Builder & Customizer 8.8 High 2026-10-27
CVE-2026-116580 Seroval: Deserialization invokes attacker-chosen callables: AsyncIteratorFactoryInstance calls source.on(listener) without type check — seroval 7.3 High 2026-10-26
CVE-2026-115912 vLLM: Public multimodal SHM handle forgery reaches worker-side `pickle.loads()` with insecure serialization disabled — vllm 7.5 High 2026-10-26
CVE-2026-115190 Mautic 任意版本存在反序列化漏洞导致远程代码执行 8.0 High 2026-10-26
CVE-2026-116230 Ndemic Creations Plague Inc Evolved Workshop Scenario Loader deserialization — Plague Inc Evolved 6.3 Medium 2026-10-26
CVE-2026-116098 SteelRaven7 Ravenfield RFL Custom Map Handler/RFLD Custom Map cacheCoverPoints deserialization — Ravenfield 6.3 Medium 2026-10-25
CVE-2026-114704 WordPress Relevanssi plugin <= 4.28.4 - PHP Object Injection vulnerability — Relevanssi 7.2 High 2026-10-24
CVE-2026-114196 WordPress Paytium plugin <= 5.0.5 - PHP Object Injection vulnerability — Paytium 9.8 Critical 2026-10-24
CVE-2026-94075 WordPress Newsletters plugin <= 4.18.1 - PHP Object Injection vulnerability — Newsletters 9.8 Critical 2026-10-24
CVE-2026-115806 Prime Mover <= 2.2.1 - Unauthenticated PHP Object Injection via Base64-Encoded Comment during Migration Search-and-Replace — Prime Mover – Backup and Migration 9.8 Critical 2026-10-24
CVE-2026-57845 Hugging Face Datasets through 5.1.0 Pickle Deserialization RCE via Pandas Builder — datasets 8.8 High 2026-10-23
CVE-2026-114624 baserCMS: PHP object injection via unguarded unserialize() in the widget-area entity — basercms 7.2 High 2026-10-23
CVE-2026-112848 WordPress Hostme v2 theme <= 7.0 - PHP Object Injection vulnerability — Hostme v2 9.8 Critical 2026-10-23
CVE-2026-112847 WordPress ZenSoul theme <= 1.13 - PHP Object Injection vulnerability — ZenSoul 9.8 Critical 2026-10-23
CVE-2026-112846 WordPress Save Life theme <= 1.2.14 - PHP Object Injection vulnerability — Save Life 9.8 Critical 2026-10-23
CVE-2026-112854 WordPress Holistic Center theme <= 1.2.6 - PHP Object Injection vulnerability — Holistic Center 9.8 Critical 2026-10-23
CVE-2026-112851 WordPress HotLock theme <= 1.3.9 - PHP Object Injection vulnerability — HotLock 9.8 Critical 2026-10-23
CVE-2026-112857 WordPress Reprizo theme <= 1.0.8 - PHP Object Injection vulnerability — Reprizo 9.8 Critical 2026-10-23
CVE-2026-112856 WordPress Vagabonds theme <= 1.3.10 - PHP Object Injection vulnerability — Vagabonds 9.8 Critical 2026-10-23
CVE-2026-112853 WordPress Hallelujah theme <= 1.1.1 - PHP Object Injection vulnerability — Hallelujah 9.8 Critical 2026-10-23
CVE-2026-112852 WordPress Helion theme <= 1.1.12 - PHP Object Injection vulnerability — Helion 8.1 High 2026-10-23
CVE-2026-112858 WordPress Rhodos theme <= 1.3.3 - PHP Object Injection vulnerability — Rhodos 9.8 Critical 2026-10-23
CVE-2026-112859 WordPress Little Birdies theme <= 1.3.16 - PHP Object Injection vulnerability — Little Birdies 9.8 Critical 2026-10-23
CVE-2026-112855 WordPress Redy theme <= 1.3.5 - PHP Object Injection vulnerability — Redy 9.8 Critical 2026-10-23
CVE-2025-30047 Remote Code Execution via Java Deserialization in CGM CLININET — CGM CLININET 9.4 Critical 2026-10-23
CVE-2026-112862 WordPress Participants Database plugin <= 2.7.8.5 - PHP Object Injection vulnerability — Participants Database 9.8 Critical 2026-10-23
CVE-2026-114608 Pylint: Arbitrary code execution via pickle deserialization of the stats cache in PYLINT_HOME — pylint 5.4 Medium 2026-10-22
CVE-2026-16477 Insecure Deserialization of .cleanshot Files in CleanShot X — CleanShot X 8.4 High 2026-10-22

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