CVE-2026-107297: msgpack5: Quadratic parsing in the streaming decoder
Impact The streaming decoder reparses an incomplete container from the beginning whenever another chunk arrives. A remote peer can split one valid MessagePack value across many small chunks, causing quadratic CPU usage and blocking the event loop. Patches The decoder now preserves incremental container state so completed elements are not parsed again when more input arrives.
Published Oct 8, 2026
Affected packages
msgpack5
- Ecosystem
- npm
- Affected
- < 6.1.0
- Fixed in
- 6.1.0
- Check
npm ls msgpack5
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
The streaming decoder reparses an incomplete container from the beginning whenever another chunk arrives. A remote peer can split one valid MessagePack value across many small chunks, causing quadratic CPU usage and blocking the event loop.
Patches
The decoder now preserves incremental container state so completed elements are not parsed again when more input arrives.
Workarounds
Buffer each complete MessagePack value before decoding it, or limit the number of chunks accepted for a single value.
Credited to SWIFI-AI.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-107296
msgpack5: Decoding negative int64 values mutates the input buffer
low3.7Oct 8, 2026CVE-2026-107298
msgpack5: Deeply nested input can exhaust the decoder stack
medium5.3Oct 8, 2026CVE-2026-107299
msgpack5: Reserved byte can cause unbounded stream buffering
medium5.9Oct 8, 2026CVE-2026-107300
msgpack5: Many buffered values can exhaust the streaming decoder stack
high7.5Oct 8, 2026CVE-2026-107301
msgpack5: Partial options disable prototype protection
medium6.5Oct 8, 2026CVE-2026-107302
msgpack5: Truncated map32 headers throw an unexpected error
high7.5Oct 8, 2026
