CVE-2026-21452: CWE-400: Uncontrolled Resource Consumption in msgpack msgpack-java
MessagePack for Java is a serializer implementation for Java. A denial-of-service vulnerability exists in versions prior to 0.9.11 when deserializing .msgpack files containing EXT32 objects with attacker-controlled payload lengths. While MessagePack-Java parses extension headers lazily, it later trusts the declared EXT payload length when materializing the extension data. When ExtensionValue.getData() is invoked, the library attempts to allocate a byte array of the declared length without enforcing any upper bound. A malicious .msgpack file of only a few bytes can therefore trigger unbounded heap allocation, resulting in JVM heap exhaustion, process termination, or service unavailability. This vulnerability is triggered during model loading / deserialization, making it a model format vulnerability suitable for remote exploitation. The vulnerability enables a remote denial-of-service attack against applications that deserialize untrusted .msgpack model files using MessagePack for Java. A specially crafted but syntactically valid .msgpack file containing an EXT32 object with an attacker-controlled, excessively large payload length can trigger unbounded memory allocation during deserialization. When the model file is loaded, the library trusts the declared length metadata and attempts to allocate a byte array of that size, leading to rapid heap exhaustion, excessive garbage collection, or immediate JVM termination with an OutOfMemoryError. The attack requires no malformed bytes, user interaction, or elevated privileges and can be exploited remotely in real-world environments such as model registries, inference services, CI/CD pipelines, and cloud-based model hosting platforms that accept or fetch .msgpack artifacts. Because the malicious file is extremely small yet valid, it can bypass basic validation and scanning mechanisms, resulting in complete service unavailability and potential cascading failures in production systems. Version 0.9.11 fixes the vulnerability.
AI Analysis
Technical Summary
MessagePack for Java (msgpack-java) is a serialization library used to encode and decode data efficiently. Versions prior to 0.9.11 contain a denial-of-service vulnerability (CVE-2026-21452) related to uncontrolled resource consumption during deserialization of .msgpack files. Specifically, when deserializing EXT32 extension objects, the library lazily parses extension headers but trusts the declared payload length metadata without enforcing any upper bounds. When the method ExtensionValue.getData() is called, the library attempts to allocate a byte array of the declared length. An attacker can craft a syntactically valid but malicious .msgpack file with an EXT32 object that declares an excessively large payload length, causing the JVM to allocate an unbounded amount of heap memory. This leads to rapid heap exhaustion, excessive garbage collection, or immediate JVM termination with an OutOfMemoryError, resulting in denial of service. The attack vector requires no malformed bytes, no user interaction, no privileges, and can be executed remotely by submitting or fetching malicious .msgpack files in environments such as model registries, inference services, CI/CD pipelines, and cloud-hosted model platforms. Because the malicious file is small and valid, it can evade basic validation and scanning, increasing the risk of successful exploitation. The vulnerability is fixed in msgpack-java version 0.9.11.
Potential Impact
For European organizations, this vulnerability poses a significant risk to the availability of services that rely on msgpack-java for deserializing .msgpack files, particularly in AI/ML model management, cloud services, and CI/CD pipelines. Exploitation can cause service outages, disrupt business operations, and potentially cascade failures in dependent systems. Organizations using vulnerable versions in critical infrastructure or cloud-hosted environments may face downtime, loss of productivity, and reputational damage. The ease of remote exploitation without authentication or user interaction increases the threat level. Additionally, the small size and validity of the malicious payload complicate detection and mitigation, potentially allowing attackers to bypass standard security controls. This can affect sectors such as finance, healthcare, manufacturing, and public services that increasingly adopt AI/ML workflows and cloud-native applications in Europe.
Mitigation Recommendations
European organizations should immediately audit their use of msgpack-java and identify any deployments running versions prior to 0.9.11. Upgrading to version 0.9.11 or later is the primary and most effective mitigation. For environments where immediate upgrade is not feasible, implement strict input validation and filtering to block or quarantine .msgpack files containing EXT32 objects or unusually large payload length declarations. Employ runtime memory usage monitoring and JVM heap limits to detect and mitigate abnormal memory allocation patterns. Integrate behavioral anomaly detection in model registries and inference services to flag suspicious deserialization activities. Use network-level controls to restrict access to services that accept .msgpack files, limiting exposure to untrusted sources. Incorporate deserialization sandboxing or isolation techniques to contain potential crashes. Finally, update incident response plans to include scenarios involving deserialization-based denial-of-service attacks.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2026-21452: CWE-400: Uncontrolled Resource Consumption in msgpack msgpack-java
Description
MessagePack for Java is a serializer implementation for Java. A denial-of-service vulnerability exists in versions prior to 0.9.11 when deserializing .msgpack files containing EXT32 objects with attacker-controlled payload lengths. While MessagePack-Java parses extension headers lazily, it later trusts the declared EXT payload length when materializing the extension data. When ExtensionValue.getData() is invoked, the library attempts to allocate a byte array of the declared length without enforcing any upper bound. A malicious .msgpack file of only a few bytes can therefore trigger unbounded heap allocation, resulting in JVM heap exhaustion, process termination, or service unavailability. This vulnerability is triggered during model loading / deserialization, making it a model format vulnerability suitable for remote exploitation. The vulnerability enables a remote denial-of-service attack against applications that deserialize untrusted .msgpack model files using MessagePack for Java. A specially crafted but syntactically valid .msgpack file containing an EXT32 object with an attacker-controlled, excessively large payload length can trigger unbounded memory allocation during deserialization. When the model file is loaded, the library trusts the declared length metadata and attempts to allocate a byte array of that size, leading to rapid heap exhaustion, excessive garbage collection, or immediate JVM termination with an OutOfMemoryError. The attack requires no malformed bytes, user interaction, or elevated privileges and can be exploited remotely in real-world environments such as model registries, inference services, CI/CD pipelines, and cloud-based model hosting platforms that accept or fetch .msgpack artifacts. Because the malicious file is extremely small yet valid, it can bypass basic validation and scanning mechanisms, resulting in complete service unavailability and potential cascading failures in production systems. Version 0.9.11 fixes the vulnerability.
AI-Powered Analysis
Technical Analysis
MessagePack for Java (msgpack-java) is a serialization library used to encode and decode data efficiently. Versions prior to 0.9.11 contain a denial-of-service vulnerability (CVE-2026-21452) related to uncontrolled resource consumption during deserialization of .msgpack files. Specifically, when deserializing EXT32 extension objects, the library lazily parses extension headers but trusts the declared payload length metadata without enforcing any upper bounds. When the method ExtensionValue.getData() is called, the library attempts to allocate a byte array of the declared length. An attacker can craft a syntactically valid but malicious .msgpack file with an EXT32 object that declares an excessively large payload length, causing the JVM to allocate an unbounded amount of heap memory. This leads to rapid heap exhaustion, excessive garbage collection, or immediate JVM termination with an OutOfMemoryError, resulting in denial of service. The attack vector requires no malformed bytes, no user interaction, no privileges, and can be executed remotely by submitting or fetching malicious .msgpack files in environments such as model registries, inference services, CI/CD pipelines, and cloud-hosted model platforms. Because the malicious file is small and valid, it can evade basic validation and scanning, increasing the risk of successful exploitation. The vulnerability is fixed in msgpack-java version 0.9.11.
Potential Impact
For European organizations, this vulnerability poses a significant risk to the availability of services that rely on msgpack-java for deserializing .msgpack files, particularly in AI/ML model management, cloud services, and CI/CD pipelines. Exploitation can cause service outages, disrupt business operations, and potentially cascade failures in dependent systems. Organizations using vulnerable versions in critical infrastructure or cloud-hosted environments may face downtime, loss of productivity, and reputational damage. The ease of remote exploitation without authentication or user interaction increases the threat level. Additionally, the small size and validity of the malicious payload complicate detection and mitigation, potentially allowing attackers to bypass standard security controls. This can affect sectors such as finance, healthcare, manufacturing, and public services that increasingly adopt AI/ML workflows and cloud-native applications in Europe.
Mitigation Recommendations
European organizations should immediately audit their use of msgpack-java and identify any deployments running versions prior to 0.9.11. Upgrading to version 0.9.11 or later is the primary and most effective mitigation. For environments where immediate upgrade is not feasible, implement strict input validation and filtering to block or quarantine .msgpack files containing EXT32 objects or unusually large payload length declarations. Employ runtime memory usage monitoring and JVM heap limits to detect and mitigate abnormal memory allocation patterns. Integrate behavioral anomaly detection in model registries and inference services to flag suspicious deserialization activities. Use network-level controls to restrict access to services that accept .msgpack files, limiting exposure to untrusted sources. Incorporate deserialization sandboxing or isolation techniques to contain potential crashes. Finally, update incident response plans to include scenarios involving deserialization-based denial-of-service attacks.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-12-29T03:00:29.277Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69583184db813ff03e011ba0
Added to database: 1/2/2026, 8:58:44 PM
Last enriched: 1/2/2026, 9:13:48 PM
Last updated: 1/8/2026, 7:22:32 AM
Views: 137
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-0700: SQL Injection in code-projects Intern Membership Management System
MediumCVE-2025-13679: CWE-862 Missing Authorization in themeum Tutor LMS – eLearning and online course solution
MediumCVE-2026-0699: SQL Injection in code-projects Intern Membership Management System
MediumCVE-2026-0698: SQL Injection in code-projects Intern Membership Management System
MediumCVE-2026-0697: SQL Injection in code-projects Intern Membership Management System
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.