Quick answers
- Is CVE-2026-105145 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105145 being exploited in the wild.
- How severe is CVE-2026-105145?
- Medium severity, with a CVSS score of 5.3, published 4 October 2026.
- Which products and versions are affected?
- Weaviate Verba up to 2.1.3.
- Is there a fix for CVE-2026-105145?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-105145 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-105145?
- Check whether you run Weaviate Verba 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.
Technical details
The /ws/generate_stream WebSocket endpoint accepts unauthenticated client connections and processes user-supplied RAG generator configurations without validating authentication or the origin. When an attacker supplies a custom OpenAI-compatible base URL and omits the API key field, the get_environment() function falls back to reading the real key from the process environment (OPENAI_API_KEY, OPENAI_EMBED_API_KEY, etc.) and sends it via Authorization header to the attacker-controlled URL. This is an authenticated SSRF that leaks live provider secrets, exploitable without authentication or user interaction.
Affected products
- Weaviate Verba up to 2.1.3
Timeline
- 2026-08-25: disclosed: Exploit published on GitHub Gist
- 2026-10-04: advisory: CVE-2026-105145 published
- 2026-06-08: other: Verba repository archived by vendor; no patch available