PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-88351 ludocode CVE debrief

An integer overflow vulnerability exists in the MPack Node API in MPack 1.1.1 on 32-bit platforms. When parsing a specially crafted MessagePack array32 or map32 object with an excessively large element count, the page allocation size calculation in mpack_tree_parse_children() can overflow size_t and produce an undersized allocation. Subsequent parsing writes mpack_node_data_t records beyond the allocated heap buffer, resulting in heap-buffer-overflow, memory corruption, and denial of service.

Vendor
ludocode
Product
MPack
CVSS
CRITICAL 9.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-24
Original CVE updated
2026-09-25
Advisory published
2026-09-24
Advisory updated
2026-09-25

Who should care

Defenders responsible for 32-bit platform deployments using the MPack library should assess exposure and prioritize verification and updates to prevent potential denial-of-service impacts.

Why it matters

The integer overflow vulnerability in the MPack Node API on 32-bit platforms can lead to denial of service and memory corruption. Defenders should prioritize verifying and updating MPack library versions, assessing exposure in 32-bit platform deployments, and monitoring for potential impacts.

  • Denial of service due to memory corruption
  • Potential for memory corruption requiring system restart or process termination
  • Verification of MPack library versions and 32-bit platform exposure

Technical summary

The MPack Node API in MPack 1.1.1 on 32-bit platforms is vulnerable to an integer overflow. When parsing a specially crafted MessagePack array32 or map32 object, the allocation size calculation can overflow, leading to an undersized allocation and subsequent heap-buffer-overflow, memory corruption, and denial of service. This vulnerability can be triggered by parsing a MessagePack array32 or map32 object with an excessively large element count, causing the page allocation size calculation in mpack_tree_parse_children() to overflow size_t and produce an undersized allocation.

Defensive priority

Defenders should prioritize verifying and updating MPack library versions, assessing exposure in 32-bit platform deployments, and monitoring for potential denial-of-service impacts.

Recommended defensive actions

  • Verify and update MPack library versions to prevent exploitation
  • Assess exposure in 32-bit platform deployments
  • Monitor for potential denial-of-service impacts
  • Implement compensating controls to mitigate potential memory corruption
  • Review relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the integer overflow vulnerability in MPack 1.1.1. GitHub repository references from ludocode support the vulnerability description. However, due to limited source detail, defenders should verify and update MPack library versions, assess exposure in 32-bit platform deployments, and monitor for potential impacts. The vulnerability can lead to denial of service and memory corruption, and defenders should prioritize verifying and updating MPack library versions, assessing exposure in 32-bit

Sources and references

Verified primary and authoritative sources

  • CVE-2026-88351 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-88351

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-88351 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-88351

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.