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-61751 NVIDIA Megatron Bridge 反序列化注入漏洞 — Megatron Bridge 7.8 High 2026-09-01
CVE-2026-61752 NVIDIA Megatron Bridge 反序列化注入漏洞 — Megatron Bridge 7.8 High 2026-09-01
CVE-2026-61754 NVIDIA Megatron Bridge 反序列化注入漏洞 — Megatron Bridge 7.8 High 2026-09-01
CVE-2026-61758 NVIDIA Megatron Bridge 反序列化注入漏洞 — Megatron Bridge 7.8 High 2026-09-01
CVE-2026-61755 NVIDIA Megatron Bridge 反序列化注入漏洞 — Megatron Bridge 7.8 High 2026-09-01
CVE-2026-61756 NVIDIA Megatron Bridge 反序列化注入漏洞 — Megatron Bridge 7.8 High 2026-09-01
CVE-2026-61757 NVIDIA Megatron Bridge 反序列化注入漏洞 — Megatron Bridge 7.8 High 2026-09-01
CVE-2026-84202 ModelScope through 1.40.0 Unsafe YAML Deserialization in Model Config Loading — modelscope 8.8 High 2026-09-01
CVE-2026-83557 jackson-databind omits java.lang.Comparable from DefaultBaseTypeLimitingValidator's unsafe base types — jackson-databind 5.6 Medium 2026-09-01
CVE-2026-82226 WordPress Tickera plugin <= 3.6.0.2 - PHP Object Injection vulnerability — Tickera 9.8 Critical 2026-08-31
CVE-2026-83497 Unrestricted Java Deserialization in OpenSearch SQL Plugin Cursor Pagination — OpenSearch 8.8 High 2026-08-31
CVE-2026-81319 Unsafe deserialization of decrypted terms enables node DoS in AshCloak — ash_cloak 5.9 Medium 2026-08-30
CVE-2026-55220 Pimcore Hotspotimage getDataFromResource() unrestricted Serialize::unserialize over object-store column — pimcore 9.3 Critical 2026-08-28
CVE-2026-81757 WordPress Rank Math SEO plugin <= 1.0.276 - Remote Code Execution (RCE) vulnerability — Rank Math SEO 7.2 High 2026-08-28
CVE-2026-82259 SvelteKit 2.49.0 before 2.53.3 Denial of Service via form — kit 7.5 High 2026-08-28
CVE-2026-82222 WordPress GiveWP plugin <= 4.16.7.1 - Remote Code Execution (RCE) vulnerability — GiveWP 10.0 Critical 2026-08-28
CVE-2026-78032 SOY CMS 反序列化注入漏洞 — SOY CMS 9.3 Critical 2026-08-28
CVE-2026-78612 Dimension SQL Injection in Scheduled Report — Dimension 8.6 High 2026-08-27
CVE-2026-78614 Dimension SQL Injection in Audit Report — Dimension 8.6 High 2026-08-27
CVE-2026-10036 SpeechBrain < 1.1.1 Arbitrary Code Execution via CKPT.yaml Parsing — speechbrain 8.8 High 2026-08-27
CVE-2026-78292 WordPress Hash Form plugin <= 1.4.1 - PHP Object Injection vulnerability — Hash Form 9.8 Critical 2026-08-27
CVE-2026-78286 WordPress Geo Controller plugin <= 8.9.8 - PHP Object Injection vulnerability — Geo Controller 9.8 Critical 2026-08-27
CVE-2026-78276 WordPress Fluent Boards Pro plugin <= 2.0.11 - PHP Object Injection vulnerability — Fluent Boards Pro 7.2 High 2026-08-27
CVE-2026-78257 WordPress Booking and Rental Manager plugin <= 2.7.5 - PHP Object Injection vulnerability — Booking and Rental Manager 8.8 High 2026-08-27
CVE-2026-80428 ILIAS PHP Object Injection via Shibboleth Logout — ILIAS 9.8 Critical 2026-08-26
CVE-2026-79657 NLTK before 3.10.3 Remote Code Execution via Unsafe Pickle Deserialization — nltk 9.8 Critical 2026-08-25
CVE-2026-56095 Insecure Deserialization in extension "Apache Solr for TYPO3 - Enterprise Search" (solr) — Extension "Apache Solr for TYPO3 - Enterprise Search" 7.7 High 2026-08-25
CVE-2026-77138 Remote Code Execution in extension "HTML5 Video Player vs. Powermail" (html5videoplayer_powermail) — Extension "HTML5 Video Player vs. Powermail" 9.3 Critical 2026-08-25
CVE-2026-78683 NLTK before 3.10.0 Remote Code Execution via Unsafe Pickle Deserialization — nltk 9.6 Critical 2026-08-25
CVE-2026-78265 WordPress The Events Calendar plugin <= 6.17.2 - PHP Object Injection vulnerability — The Events Calendar 9.8 Critical 2026-08-24

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