The server exposes an unauthenticated agent endpoint on all interfaces, and headless startup automatically approves tools by default. This creates a serious remote-execution risk when the server is reachable; the package’s intended server functionality makes this a critical vulnerability rather than clear malicious intent.
Static reason
No blocking static signals were detected.
Trigger
A user starts the server or daemon in a headless environment and a remote caller can reach its listening port.
Impact
A remote caller may use the configured agent and its project access to trigger tool actions, including potentially executing commands or accessing project data.
Mechanism
The server binds to all interfaces; its message endpoint forwards caller prompts to the orchestrator, while headless startup enables automatic tool approval by default. No authentication gate was found in the inspected server middleware or route handling.
Evidence
dist/index.jsdist/routes/messages.jsdist/middleware/cors.js
Network endpoints2
0.0.0.0:<PORT> (default 4000)/v1/messages