https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 01:12:37 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-107298 <p>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.</p> <p>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.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-107298 https://vulnerability.circl.lu/vuln/ghsa-24ch-f2g6-9hhh <p><strong>Affected:</strong> npm: msgpack5</p> <p>### Impact</p> <p>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.</p> <p>### Patches</p> <p>The decoder now limits nesting depth to 100 by default and throws `Maximum decode depth exceeded`. Applications can configure the limit with the `maxDepth` option.</p> <p>### Workarounds</p> <p>Reject deeply nested input before decoding, isolate decoding in a worker, or enforce a trusted schema with a bounded nesting depth.</p> <p><strong>Affected:</strong> npm: msgpack5</p> <p>### Impact</p> <p>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.</p> <p>### Patches</p> <p>The decoder now limits nesting depth to 100 by default and throws `Maximum decode depth exceeded`. Applications can configure the limit with the `maxDepth` option.</p> <p>### Workarounds</p> <p>Reject deeply nested input before decoding, isolate decoding in a worker, or enforce a trusted schema with a bounded nesting depth.</p> https://vulnerability.circl.lu/vuln/ghsa-24ch-f2g6-9hhh