← All advisories
CVE-2026-114107criticalCode execution2026-10-21

HKUDS Vibe-Trading before 0.1.7: unauthenticated API, prompt-injectable shell tools running as root and unrestricted file reads (CVE-2026-114107, CVE-2026-114106)

Three GitHub advisories for the vibe-trading-ai package (HKUDS Vibe-Trading) cover 0.1.0 up to 0.1.6. With the shipped config the FastAPI server needs no API key and runs as root in Docker on 0.0.0.0:8899; the agent's BashTool and BackgroundRunTool run model-written commands with shell=True and no approval, so instructions planted in a document or web page give root shell; and read_document has no sandbox at all. Fixed in 0.1.7.

01.

What it is

GHSA-v2f8-6655-7grj (Critical): API_AUTH_KEY ships commented out and require_auth() returns early when it is unset, so every endpoint is unauthenticated. The advisory also covers a read-side authorization gap that stays even with a key set, unauthenticated writes of .py/.sh/.yaml files, permissive CORS for localhost pages, and partial API-key disclosure. The Dockerfile has no USER, so the server runs as root.

GHSA-jqmf-mx4f-hfr6 / CVE-2026-114107 (Critical; NVD 8.8): BashTool and BackgroundRunTool pass commands from the model to subprocess.run(shell=True) with no allow-list or confirmation; backtest exec_module() runs top-level code before its class check; read_url fetches any URL (SSRF); and Jinja2 codegen has autoescape off. Indirect prompt injection in content the agent reads is enough to run commands.

GHSA-5rmq-chc7-m22f / CVE-2026-114106 (High; NVD 7.5): read_document() calls no sandbox check, and safe_user_path() accepts anything under the home or working directory, which in the container is /root and /app, so the agent can be told to return /etc/shadow, /proc/self/environ (API keys), /root/.ssh/id_rsa or /app/agent/.env.

All three list vibe-trading-ai >= 0.1.0, < 0.1.7 as affected and 0.1.7 as patched.

02.

How to check

  1. Run `pip show vibe-trading-ai`, or check the image tag / git tag of your Vibe-Trading deployment.
  2. Check whether port 8899 is reachable from other machines and whether API_AUTH_KEY is set in agent/.env.
03.

How to fix

  1. Upgrade to vibe-trading-ai 0.1.7 or later.
  2. Set API_AUTH_KEY, bind the API to 127.0.0.1 or put it behind an authenticating proxy, and run the container as a non-root user.
  3. If an older version was exposed, rotate the LLM API keys and other secrets in agent/.env and any credentials under /root in the container.
pip show vibe-trading-ai | grep -i ^version
grep -n '^API_AUTH_KEY' agent/.env || echo 'API_AUTH_KEY not set'
04.

Sources

The weekly email

One email a week. Only what changed.

Every new security hole in AI coding tools, MCP servers, app builders and the stacks they generate (Next.js, Supabase, Node, PHP), each with how to check your app and the fix. No roundups of things you already read.

Free, one email a week. Read the latest issue first if you like. One-click unsubscribe in every email. We never sell or share addresses.