p PatchFirst

PatchFirst · Latest vulnerabilities

msgpack5 vulnerabilities

Vulnerabilities published for msgpack5 in the last 30 days: 7. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 8

  1. CVE-2026-107302

    High · CVSS 7.5EPSS 0.52%Fix available

    msgpack5: Truncated map32 headers throw an unexpected error

    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 RangeError instead of IncompleteBufferError, which can unexpectedly terminate a request, stream, or worker in applications that wait for additional bytes after IncompleteBufferError. There is no adjacent-memory disclosure because the buffer implementation checks bounds. This issue is fixed in version 6.1.0.

    • Update to 6.1.0
    Published Updated
  2. CVE-2026-107301

    Medium · CVSS 6.5EPSS 0.37%Fix available

    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, potentially changing inherited properties or downstream behavior, although Object.prototype is not modified globally. This issue is fixed in version 6.1.0.

    • Update to 6.1.0
    Published Updated
  3. CVE-2026-107300

    High · CVSS 7.5EPSS 0.43%Fix available

    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 the value count, exhausting the JavaScript call stack, and interrupting the process or stream. This issue is fixed in version 6.1.0.

    • Update to 6.1.0
    Published Updated
  4. CVE-2026-107299

    Medium · CVSS 5.9EPSS 0.39%Fix available

    msgpack5: Reserved byte can cause unbounded stream buffering

    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 cannot make the value valid, allowing a remote peer to exhaust memory. This issue is fixed in version 6.1.0.

    • Update to 6.1.0
    Published Updated
  5. CVE-2026-107298

    Medium · CVSS 5.3EPSS 0.37%Fix available

    msgpack5: Deeply nested input can exhaust the decoder stack

    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 process, worker, or request handler. This issue is fixed in version 6.1.0.

    • Update to 6.1.0
    Published Updated
  6. CVE-2026-107297

    Medium · CVSS 5.9EPSS 0.39%Fix available

    msgpack5: Quadratic parsing in the streaming decoder

    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 elements to be decoded repeatedly, producing quadratic CPU use and blocking the event loop. This issue is fixed in version 6.1.0.

    • Update to 6.1.0
    Published Updated
  7. CVE-2026-107296

    Low · CVSS 3.7EPSS 0.28%Fix available

    msgpack5: Decoding negative int64 values mutates the input buffer

    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, logging, or later processing can observe silently corrupted data, while positive integers and other MessagePack value types are unaffected. This issue is fixed in version 6.1.0.

    • Update to 6.1.0
    Published Updated
  8. CVE-2021-21368

    Medium · CVSS 6.7EPSS 1.65%Fix available

    Prototype poisoning

    msgpack5 is a msgpack v5 implementation for node.js and the browser. In msgpack5 before versions 3.6.1, 4.5.1, and 5.2.1 there is a "Prototype Poisoning" vulnerability. When msgpack5 decodes a map containing a key "__proto__", it assigns the decoded value to __proto__. Object.prototype.__proto__ is an accessor property for the receiver's prototype. If the value corresponding to the key __proto__ decodes to an object or null, msgpack5 sets the decoded object's prototype to that value. An attacker who can submit crafted MessagePack data to a service can use this to produce values that appear to be of other types; may have unexpected prototype p

    • Update to 3.6.1
    • Update to 4.5.1
    • Update to 5.2.1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →