Intel

AIKIDO-2026-648841

@circleci/mcp-server-circleci is vulnerable to Command Injection

Command InjectionGHSA-m9x7-h9px-p447 Published 2 days ago

98

Critical Risk

This Affects:

JS@circleci/mcp-server-circleci
0.0.1 - 0.16.0
Fixed in 0.16.1
Are you affected? Scan for Free

TL;DR

The run_evaluation_tests tool builds a CircleCI pipeline configuration from caller-supplied input and submits it to the CircleCI API for execution. The promptFiles[].fileName value is accepted as an unconstrained string and interpolated unquoted into shell commands inside the generated config, so a caller who controls fileName can inject arbitrary shell that runs in the CircleCI job under the server's CircleCI token. In the documented shared-token remote deployment mode the server requires no authentication, so an unauthenticated network client can reach the sink and gain command execution with the token's full CI/CD access. The fix constrains fileName to a strict character allowlist at the schema boundary, single-quotes it at every interpolation site, and makes remote request authentication required by default.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and callers can invoke the run_evaluation_tests tool, for example the documented shared-token remote deployment where the server is unauthenticated.

Background info

@circleci/mcp-server-circleci is vulnerable to Command Injection in versions 0.0.1 - 0.16.0.

How to fix this

Upgrade the @circleci/mcp-server-circleci library to the patch version.