The default non-TTY configuration combines a listener on all interfaces with automatic tool approval, and the messages route shows no authentication middleware. This creates a serious exposure when the server is reachable from an untrusted network, though the source does not establish malicious intent or that every deployment is externally reachable.
Static reason
No blocking static signals were detected.
Trigger
Starting the server in non-TTY mode, including through the daemon command; the behavior is on by default unless approval is explicitly disabled.
Impact
A reachable caller may be able to invoke the agent and its tools using the server host's permissions, potentially enabling unauthorized local actions or code execution.
Mechanism
The server binds to all interfaces and the messages endpoint has no visible authentication middleware. Non-TTY startup enables yolo mode, bypassing interactive tool approval.
Evidence
bin/cortex-daemon.jsdist/index.jsdist/routes/messages.js
Network endpoints1
0.0.0.0:4000 (default; PORT can override)