Vulnerabilities

Vulnerability · CVE-2026-114108

Vibe-Trading FastAPI endpoints permit unauthenticated access, file upload, and an RCE chain

Published Oct 2, 2026 · catalog updated Oct 21, 2026 · Vibe-Trading FastAPI endpoints permit

Open the advisory

Exploitation likelihood is not on this record for CVE-2026-114108. A missing EPSS score is not a low risk. Compare Vibe-Trading FastAPI endpoints permit with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Vibe-Trading FastAPI endpoints permit).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Critical10.0
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
PyPI vibe-trading-ai

### Summary: 5 findings — unauthenticated full-API exposure (F1, lead Critical), read-side authorization gap that persists even with set (F2), unauthenticated file write of / / to a server-returned path (F3), default-permissive CORS that combines with a loopback-only check to grant any browser page on whitelisted localhost ports credentialed cross-origin access (F-A4), and partial API-key disclosure via (F-A5). --- ### Shared baseline (applies to all 5 findings) The shipped line 112 ships commented out. at line 303 executes and returns immediately when is unset, so every endpoint decorated with operates as unauthenticated. The shipped does **not** contain a directive, so the FastAPI process runs as inside the container (verified: returns ). The binds with no network restriction. The only operator action required beyond a clean install is supplying a working LLM API key so the agent loop can complete its tool-call round trip — this is the normal first step to make the agent functional, not an additional security opt-in. F-A4 and F-A5 do *not* require an LLM key (see per-finding notes); F1 and F3 do not require an LLM key for the unauth surface itself, only for the chained RCE demonstration in F1. ### Reproducer environment (common) > **Note on the placeholder used throughout the per-finding "Steps to observe" blocks below**: replace with the address you reach the docker host on — typically (or ) if you are running the reproducer on the same machine as the container. All commands below assume this substitution. --- ### Finding 1 — Critical: Unauthenticated network client reaches shell execution via POST /sessions/{id}/messages - **Severity**: Critical - **CVSS v3.1**: 9.8 — - **CVSS v4.0**: 10.0 — - **CWE**: CWE-306 (Missing Authentication for Critical Function); chains into CWE-78 (Group B, F6) **Affected files**: - — early return in - — (the dependency is a no-op when is unset) - — with command read from (full bug detail tracked in GHSA-2 / Group B / F6) **Intent vs

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • PyPI vibe-trading-ai0.1.0 → 0.1.7

How to fix CVE-2026-114108

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for CVE-2026-114108. A missing EPSS score is not a low risk. Compare Vibe-Trading FastAPI endpoints permit with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0.1.0 → 0.1.7. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-200: Exposure of Sensitive Information; CWE-306: Missing Authentication for Critical Function; CWE-434: Unrestricted Upload of File with Dangerous Type. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 2, 2026 · GitHub Advisory Database

    Detected

    ### Summary: 5 findings — unauthenticated full-API exposure (F1, lead Critical), read-side authorization gap that persists even with set (F2), unauthenticated file write of / / to a server-returned path (F3), default-permissive CORS that combines with a loopback-only check to grant any browser page on whitelisted localhost ports credentialed cross-origin access (F-A4), and partial API-key disclosu

  2. Oct 21, 2026 · GitHub Advisory Database

    Fix available

    vibe-trading-ai fixed in 0.1.7

  3. Oct 21, 2026 · GitHub Advisory Database

    Fix available

    vibe-trading-ai fixed in 0.1.7

  4. Oct 21, 2026 · GitHub Advisory Database

    Updated

    ### Summary: 5 findings — unauthenticated full-API exposure (F1, lead Critical), read-side authorization gap that persists even with set (F2), unauthenticated file write of / / to a server-returned path (F3), default-permissive CORS that combines with a loopback-only check to grant any browser page on whitelisted localhost ports credentialed cross-origin access (F-A4), and partial API-key disclosu

Sources

References

Freshness

Last verified in this catalog Oct 21, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.