Quick answers
- Is CVE-2026-114106 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114106 being exploited in the wild.
- How severe is CVE-2026-114106?
- High severity, with a CVSS score of 7.5, published 21 October 2026.
- Which products and versions are affected?
- HKUDS Vibe-Trading 0.1.0 before 0.1.7.
- Is there a fix for CVE-2026-114106?
- Yes: fixed in 0.1.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114106 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-114106?
- Check whether you run HKUDS Vibe-Trading at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.1.7
Technical details
The vulnerability exists in two file-read tool functions: read_document() has no path sanitization and returns any file readable by the FastAPI process; safe_user_path() accepts any path under Path.home() or Path.cwd(), which resolve to /root and /app inside the shipped container, exposing credential files and environment variables. The LLM agent auto-discovers these tools and makes them callable without proper sandbox restrictions. Because the container runs as root with no USER directive, the process can access system files including /etc/shadow, /proc/self/environ, and credential files in /root and /app.
Affected products
- HKUDS Vibe-Trading 0.1.0 before 0.1.7
Timeline
- 2026-07-29: disclosed
- 2026-10-21: advisory