Netkingj

The stable publish workflow interpolates `steps.release.outputs.body` directly into a Bash echo command before writing the RAW RELEASE.md file. This allows shell metacharacters controlled by a contributor in the release-note text to execute when a maintainer initiates a stable release. Such execution can lead to the modification of workspace scripts or generated artifacts, potentially impacting subsequent release steps that possess write permissions and the `GITHUB TOKEN`.

The HTTP mode of @tsparticles/mcp-server contains a flaw where `JSON.parse` is called outside a request-local error boundary within the POST '/mcp' endpoint. An unauthenticated user can send a malformed JSON body, triggering a SyntaxError that terminates the Node.js process. This results in a denial of service, making the MCP service unavailable until it is restarted by an external supervisor.

The HTTP mode of the server reuses a single stateful `StreamableHTTPServerTransport` for every client. An unauthenticated client can claim the shared transport state by sending an initial initialize request without an `mcp-session-id`. This action causes subsequent independent clients to receive a Server already initialized error, preventing them from establishing sessions until the process is restarted, although the first client's session remains functional.

The issue is related to an improper authorization vulnerability that allows physical attackers to partially bypass the factory reset protection. This vulnerability can be exploited by physical attackers.

The issue is related to improper access control, allowing a physical attacker to install a package before the completion of the Setup wizard. This can be exploited by a physical attacker.

The issue is related to an Improper Protection of Alternate Path vulnerability in the Setup wizard process. This vulnerability allows a physical attacker to install packages before finishing the Setup wizard.