Vibe-Trading AI versions >=0.1.0 and <0.1.7 suffer from multiple security flaws. The most critical is an unauthenticated remote code execution vulnerability (CWE-306 leading to CWE-78) via the POST /sessions/{id}/messages endpoint. This occurs because the require_auth() function returns immediately without enforcing authentication if the API_AUTH_KEY environment variable is unset, making authentication dependencies ineffective. The LLM agent executes shell commands using subprocess.run with shell=True as root inside the container, allowing arbitrary command execution. Additional vulnerabilities include unauthenticated file uploads of executable scripts, overly permissive CORS policies enabling credentialed cross-origin access from localhost ports, and partial API key disclosure via masking functions. The Dockerfile lacks a USER directive, so the FastAPI process runs as root inside the container, exacerbating the risk. The vulnerabilities affect versions from 0.1.0 up to but not including 0.1.7. A patch is available.

An unauthenticated attacker with network access to port 8899 can execute arbitrary shell commands as root inside the container, resulting in full container compromise. This can lead to complete loss of confidentiality, integrity, and availability of the affected system. Additional vulnerabilities allow unauthorized file uploads and information disclosure, increasing the attack surface. The default root execution context of the container amplifies the severity of the remote code execution.

A patch is available for these vulnerabilities. Operators should apply the official fix to ensure authentication is properly enforced and to restrict file uploads and CORS policies. Until patched, do not expose port 8899 to untrusted networks. Configure the Docker container to run the FastAPI process as a non-root user by adding a USER directive in the Dockerfile. Verify that the API_AUTH_KEY environment variable is set to enforce authentication. Review and restrict CORS settings to prevent unauthorized cross-origin requests. Follow the vendor advisory for detailed remediation steps.