目标达成 感谢每一位支持者 — 我们达成了 100% 目标！

目标: 1000 元 · 已筹: 1336 元

100%
请我们喝杯咖啡

CWE-502 可信数据的反序列化 类漏洞列表 2189

CWE-502 可信数据的反序列化 类弱点 2189 条 CVE 漏洞汇总，含 AI 中文分析。

CWE-502 指反序列化不可信数据漏洞，属于数据验证缺陷。攻击者通过构造恶意序列化对象，在系统反序列化时触发任意代码执行或拒绝服务。开发者应避免直接反序列化外部输入，改用 JSON 等安全格式，或实施严格的类白名单校验与完整性检查，确保反序列化过程仅处理预期类型，从而阻断恶意载荷执行。

MITRE CWE 官方描述
CWE：CWE-502 反序列化不可信数据 (Deserialization of Untrusted Data) 英文：产品在没有充分确保生成的数据有效性的情况下，对不可信数据进行反序列化。
常见影响 (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…
缓解措施 (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…
代码示例 (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 标题 CVSS 风险等级 Published
CVE-2025-33253 NVIDIA Nemo Framework 代码问题漏洞 — NeMo Framework 7.8 High 2026-02-18
CVE-2025-33252 NVIDIA Nemo Framework 代码问题漏洞 — NeMo Framework 7.8 High 2026-02-18
CVE-2025-33245 NVIDIA Nemo Framework 代码问题漏洞 — NeMo Framework 8.0 High 2026-02-18
CVE-2025-33243 NVIDIA Nemo Framework 代码问题漏洞 — NeMo Framework 7.8 High 2026-02-18
CVE-2025-33241 NVIDIA Nemo Framework 代码问题漏洞 — NeMo Framework 7.8 High 2026-02-18
CVE-2026-26220 LightLLM 代码问题漏洞 — LightLLM 9.8AI Critical AI 2026-02-17
CVE-2026-2555 JeecgBoot 代码问题漏洞 — JeecgBoot 5.0 Medium 2026-02-16
CVE-2026-26208 ADB Explorer 代码问题漏洞 — ADB-Explorer 7.8 High 2026-02-13
CVE-2026-26221 Hyland Software Hyland OnBase 安全漏洞 — OnBase Workflow Timer Service 9.8 Critical 2026-02-13
CVE-2026-26215 Manga/Image Translator 代码问题漏洞 — manga-image-translator 9.8AI Critical AI 2026-02-11
CVE-2026-0910 WordPress plugin wpForo Forum 代码问题漏洞 — wpForo Forum 8.8 High 2026-02-11
CVE-2026-21511 Microsoft Outlook 代码问题漏洞 — Microsoft 365 Apps for Enterprise 7.5 High 2026-02-10
CVE-2026-21531 Microsoft Azure SDK 代码问题漏洞 — Azure AI Language Authoring 9.8 Critical 2026-02-10
CVE-2026-23685 SAP NetWeaver 代码问题漏洞 — SAP NetWeaver (JMS service) 4.4 Medium 2026-02-10
CVE-2026-25925 PowerDocu 代码问题漏洞 — PowerDocu 7.8 High 2026-02-09
CVE-2026-2113 tpAdmin 代码问题漏洞 — tpadmin 7.3 High 2026-02-07
CVE-2026-25632 EPyT-Flow 代码问题漏洞 — EPyT-Flow 10.0 Critical 2026-02-06
CVE-2020-37071 CraftCMS 3 vCard Plugin 代码问题漏洞 — CraftCMS 9.8 Critical 2026-02-03
CVE-2026-25615 Blesta 代码问题漏洞 — Blesta 7.2 High 2026-02-03
CVE-2026-25614 Blesta 代码问题漏洞 — Blesta 7.5 High 2026-02-03
CVE-2026-24954 WordPress plugin WpEvently 安全漏洞 — WpEvently 8.8 High 2026-02-03
CVE-2026-1691 bolo-solo 代码问题漏洞 — bolo-solo 6.3 Medium 2026-01-30
CVE-2025-40553 SolarWinds Web Help Desk 代码问题漏洞 — Web Help Desk 9.8 Critical 2026-01-28
CVE-2025-40551 SolarWinds Web Help Desk 代码问题漏洞 — Web Help Desk 9.8 Critical 2026-01-28
CVE-2026-24765 PHPUnit 代码问题漏洞 — phpunit 7.8 High 2026-01-27
CVE-2026-24747 PyTorch 代码问题漏洞 — pytorch 8.8 High 2026-01-27
CVE-2026-24656 Apache Karaf Decanter 安全漏洞 — Apache Karaf 9.1AI Critical AI 2026-01-26
CVE-2025-15351 Anritsu VectorStar 代码问题漏洞 — VectorStar 7.8 - 2026-01-23
CVE-2025-15350 Anritsu VectorStar 代码问题漏洞 — VectorStar 7.8 - 2026-01-23
CVE-2025-15348 Anritsu ShockLine 代码问题漏洞 — ShockLine 7.8 - 2026-01-23

CWE-502（可信数据的反序列化） 是常见的弱点类别，本平台收录该类弱点关联的 2189 条 CVE 漏洞。