MessagePack for Java Vulnerable to Remote DoS via Malicious EXT Payload Allocation
CVE-2026-21452GHSA-cw39-r4h6-8j3x
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.msgpack:msgpack-core 0.9.11), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.msgpack:msgpack-core
- Affected
- < 0.9.11
- Fixed in
- 0.9.11
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-cw39-r4h6-8j3x lists affected ranges: Maven org.msgpack:msgpack-core >=0 <0.9.11
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- CVE-2026-21452: 0.60% estimated exploitation activity in the next 30 days; percentile 48.88 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary Affected Components: A denial-of-service vulnerability exists in MessagePack for Java 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. PoC Download dependency: curl -LO https://repo1.maven.org/maven2/org/msgpack/msgpack-core/0.9.8/msgpack-core-0.9.8.jar Java Reproducer Compile Run (with limited heap) Observed Result: Run: A…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-cw39-r4h6-8j3x
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-21452 Advisory: MessagePack for Java Vulnerable to Remote DoS via Malicious EXT Payload Allocation IDs: CVE-2026-21452, GHSA-cw39-r4h6-8j3x Record: https://patchnext.com/advisories/cve-2026-21452 (revision 1, source checked 26 Oct 2026, 16:43 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.msgpack:msgpack-core 0.9.11. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.msgpack:msgpack-core: affected < 0.9.11; fixed in 0.9.11 ## Suggested inspection (read-only) - Maven org.msgpack:msgpack-core: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.msgpack:msgpack-core. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-cw39-r4h6-8j3x (GitHub-reviewed advisory GHSA-cw39-r4h6-8j3x lists affected ranges: Maven org.msgpack:msgpack-core >=0 <0.9.11) Commands are suggestions: review each one before running it.
Loading voting…