Live › vulnerability › CVE-2026-107685
Go to dashboardThe Elixir req_llm library's WebSocket streaming client connects to OpenAI without verifying the server's TLS certificate, and it blocks callers from turning verification on. An attacker on the network path can read and change OpenAI WebSocket sessions and capture the API key or OAuth token sent in the authorization header.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Check the req_llm version in mix.lock: affected if it is from 1.9.0 before 1.29.0 and the app uses the OpenAI Responses, Realtime, or Codex WebSocket paths.
Upgrade req_llm to 1.29.0 or later, then rotate any OpenAI API keys or OAuth tokens that were sent over these WebSocket paths.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-107685")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.