A security flaw has been discovered in mcollina mcp-ripgrep up to 0.4.0. Affected is an unknown function of the file src/index.ts of the component Advanced Search Tool. The manipulation of the argument fileType results in os command injection. The attack requires a local approach. The exploit has been released to the public and may be used for attacks. The real existence of this vulnerability is still doubted at the moment. The code's own escapeShellArg on sibling arguments (skipped only for fileType) indicates that this is a CWE-78 oversight, not a documented design. The project maintainer cites the documentation: "This MCP server executes shell commands using the ripgrep tool. While efforts have been made to safely escape arguments, use caution when providing input, as it runs commands on your machine."
CVE-2026-107302 is an out-of-bounds read vulnerability in the msgpack5 library for Node.js and browsers. Versions prior to 6.1.0 improperly read the length of a map32 value before fully validating the header, causing a RangeError instead of the expected IncompleteBufferError on truncated input. This can unexpectedly terminate requests, streams, or workers that rely on the IncompleteBufferError to wait for more data. The issue does not lead to memory disclosure and is fixed in version 6.1.0.
A prototype pollution vulnerability exists in msgpack5 versions prior to 6.1.0. When constructed with an empty or partial options object, the default protection against prototype pollution is disabled. This allows a decoded map containing a __proto__ key to replace the decoded object's prototype, potentially altering inherited properties or downstream behavior. The global Object.prototype is not affected. The issue is fixed in version 6.1.0.
### 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 values iteratively with constant call-stack depth.
### Workarounds
Limit the number of MessagePack values accepted in one chunk, or split large batches before passing them to the decoder stream.
A vulnerability in msgpack5 prior to version 6.1.0 allows a remote attacker to cause a denial of service by exhausting memory. The streaming decoder incorrectly treats the reserved MessagePack byte 0xc1 as incomplete input rather than invalid, causing it to buffer data indefinitely while waiting for bytes that will never form a valid value. This issue is fixed in version 6.1.0.
msgpack5 versions prior to 6.1.0 have an uncontrolled recursion vulnerability in their array and map decoding paths. This allows an attacker to submit deeply nested MessagePack input that exhausts the JavaScript call stack, causing process interruption. The issue is fixed in version 6.1.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.
CVE-2026-107296 is a low-severity vulnerability in the msgpack5 library for Node.js and browsers. Before version 6.1.0, decoding a negative signed 64-bit integer causes modification of the input buffer bytes used for decoding. This silent corruption affects applications that reuse or retain the encoded input for integrity checks, logging, or later processing. Positive integers and other MessagePack types are not affected. The issue is fixed in msgpack5 version 6.1.0.