# Vibe-Trading FastAPI endpoints permit unauthenticated access, file upload, and an RCE chain Advisory record · `GHSA-v2f8-6655-7grj` - **Identifiers:** `GHSA-v2f8-6655-7grj` · `CVE-2026-114108` - **State:** Confirmed - **Severity:** CVSS 9.3 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-306](https://cwe.mitre.org/data/definitions/306.html) · [CWE-434](https://cwe.mitre.org/data/definitions/434.html) · [CWE-862](https://cwe.mitre.org/data/definitions/862.html) · [CWE-942](https://cwe.mitre.org/data/definitions/942.html) - **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [Unrestricted file upload](https://agentprime.io/advisories/tag/file-upload.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [CWE-942](https://agentprime.io/advisories/tag/cwe-942.md) - **Published:** 2 Oct 2026 - **Updated:** 21 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 2 Oct 2026, 22:44 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 9.3: 9.0 or more. How we decide what’s critical: ## Affected packages - `vibe-trading-ai` (PyPI): affected `>=0.1.0, <0.1.7`; fixed in `0.1.7` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > vibe-trading-ai versions 0.1.0 before 0.1.7 expose API endpoints without authentication when API_AUTH_KEY is unset, which is the shipped default. A network attacker can read session history, upload files, and chain these into running shell commands as root in the container. Upgrade to vibe-trading-ai 0.1.7. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 9.3 Critical, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`, from CNA (VulnCheck) - **CISA KEV:** Not listed. - **EPSS:** 0.0053, the 44th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:08 UTC: First seen by agentprime - 31 Oct 2026, 14:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-v2f8-6655-7grj) ## Sources - [GitHub Advisory Database: GHSA-v2f8-6655-7grj](https://github.com/advisories/GHSA-v2f8-6655-7grj) - [OSV: GHSA-v2f8-6655-7grj](https://osv.dev/vulnerability/GHSA-v2f8-6655-7grj) - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .