Improper Certificate Validation vulnerability in the WebSocket streaming client in agentjido req_llm allows an on-path attacker to read a…
CVE-2026-107685 · GHSA-w53j-6pxf-r2vw · EUVD-2026-108709 · published 23 Oct 2026
How serious is it
- Severity: critical, CVSS score 9.1 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-107685?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- agentjido req_llm: a389d718640ceb2d541a8f540ab954cbf5ef8313 <c7264fc0217fbacfb5562234ff790b8e4462de76
- agentjido req_llm: 1.9.0 <1.29.0
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
Improper Certificate Validation vulnerability in the WebSocket streaming client in agentjido req_llm allows an on-path attacker to read and modify OpenAI WebSocket sessions, including the authorization bearer token, via a TLS certificate the client does not trust. ReqLLM.Streaming.WebSocketSession.Client.start/3 in lib/req_llm/streaming/web_socket_session/client.ex starts WebSockex without TLS options, and WebSockex defaults to insecure: true, which connects with verify: :verify_none. The option allowlist also drops any caller-supplied cacerts or ssl_options, so an application cannot turn verification on.
The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the authorization header. HTTP streaming through Finch and the HTTP/2 duplex session through Mint verify certificates and are not affected.
This issue affects req_llm: from 1.9.0 before 1.29.0.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- github.com/agentjido/req_llm/security/advisories/GHSA-6vww-5m28-f26v
- cna.erlef.org/cves/CVE-2026-107685.html
- osv.dev/vulnerability/EEF-CVE-2026-107685
- github.com/agentjido/req_llm/commit/a389d718640ceb2d541a8f540ab954cbf5ef8313
- github.com/agentjido/req_llm/commit/c7264fc0217fbacfb5562234ff790b8e4462de76
Merged from ENISA EUVD. Last updated 23 Oct 2026. All vulnerabilities · RSS · JSON