CVE-2026-107302

msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, the decoder reads the four-byte length of a map32 value before validating that the complete five-byte header is available. A truncated map32 header therefore causes a checked out-of-bounds buffer read and throws...

msgpack5: Many buffered values can exhaust the streaming decoder stack

Impact The streaming decoder recursively invokes itself for every complete value remaining in a chunk. A single chunk containing many small valid MessagePack values can exhaust the JavaScript call stack and interrupt the process or stream. Patches The streaming decoder now drains concatenated...

NPM: msgpack5: Many buffered values can exhaust the streaming decoder stack

NPM: msgpack5: Many buffered values can exhaust the streaming decoder stack vulnerability discovered by ? in WordPress Npm msgpack5 versions 6.1.0...

NPM: msgpack5: Deeply nested input can exhaust the decoder stack

NPM: msgpack5: Deeply nested input can exhaust the decoder stack vulnerability discovered by ? in WordPress Npm msgpack5 versions 6.1.0...

msgpack5: Deeply nested input can exhaust the decoder stack

Impact The decoder has no nesting-depth limit for arrays and maps. An attacker who can provide MessagePack input can use deeply nested containers to exhaust the JavaScript call stack and interrupt the process or request handler. Patches The decoder now limits nesting depth to 100 by default and...

CVE-2026-107300

msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, the streaming decoder recursively invokes itself for each complete MessagePack value remaining in a chunk. A remote peer can send one chunk containing many small valid values, causing recursion proportional to th...

CVE-2026-107301

msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, constructing msgpack5 with an empty or partial options object disables the default protoAction: 'error' protection. A decoded map containing a proto key can then replace the decoded object's prototype, potentiall...

CVE-2026-107296

msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, decoding a negative signed 64-bit integer modifies the corresponding bytes in the caller-provided input buffer while computing the value. Applications that retain or reuse encoded input for integrity checks,...

CVE-2026-107297

msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, the streaming decoder reparses an incomplete array or map from the beginning whenever another chunk arrives. A remote peer can split one valid MessagePack container across many small chunks, causing completed...

CVE-2026-107299

msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, the streaming decoder treats the reserved MessagePack byte 0xc1 as incomplete input instead of invalid input. When 0xc1 begins a stream, subsequent data remains buffered while the decoder waits for bytes that...

CVE-2026-107298

msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, the array and map decoding paths have no nesting-depth limit, allowing an attacker who can provide MessagePack input to submit deeply nested containers that exhaust the JavaScript call stack and interrupt a...

EUVD-2026-95114

msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, the decoder reads the four-byte length of a map32 value before validating that the complete five-byte header is available. A truncated map32 header therefore causes a checked out-of-bounds buffer read and throws...

CVE-2026-107302

The msgpack5 library (a msgpack v5 implementation for Node.js and browsers) contains a vulnerability where the decoder reads a four-byte length of a map32 value before confirming the full five-byte header is present. This leads to a checked out-of-bounds buffer read, causing a RangeError instead ...

CVE-2026-107301

The msgpack5 library, a msgpack v5 implementation for Node.js and browsers, is vulnerable to prototype pollution in versions prior to 6.1.0 . The root cause is that constructing the library with an empty or partial options object disables the default protoAction: 'error' protection. This allows a...

EUVD-2026-95112

msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, constructing msgpack5 with an empty or partial options object disables the default protoAction: 'error' protection. A decoded map containing a proto key can then replace the decoded object's prototype, potentiall...

CVE-2026-107301 msgpack5: Partial options disable prototype protection

msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, constructing msgpack5 with an empty or partial options object disables the default protoAction: 'error' protection. A decoded map containing a proto key can then replace the decoded object's prototype, potentiall...

EUVD-2026-95111

msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, the streaming decoder recursively invokes itself for each complete MessagePack value remaining in a chunk. A remote peer can send one chunk containing many small valid values, causing recursion proportional to th...

CVE-2026-107300

The msgpack5 library, a msgpack v5 implementation for node.js and the browser , is vulnerable to a stack exhaustion issue in versions prior to 6.1.0 . The streaming decoder recursively invokes itself for every complete MessagePack value found within a chunk. A remote peer can exploit this by send...

CVE-2026-107300 msgpack5: Many buffered values can exhaust the streaming decoder stack

msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, the streaming decoder recursively invokes itself for each complete MessagePack value remaining in a chunk. A remote peer can send one chunk containing many small valid values, causing recursion proportional to th...

EUVD-2026-95110

msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, the streaming decoder treats the reserved MessagePack byte 0xc1 as incomplete input instead of invalid input. When 0xc1 begins a stream, subsequent data remains buffered while the decoder waits for bytes that...