WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers

Summary

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.

Remediation

1. Inventory every agentjido req_llm deployment, including staging.
2. Upgrade agentjido req_llm to 1.29.0.
3. Confirm the running version after the upgrade.

References

• Patchhttps://github.com/agentjido/req_llm/commit/c7264fc0217fbacfb5562234ff790b8e4462de76
• Advisoryhttps://github.com/agentjido/req_llm/security/advisories/GHSA-6vww-5m28-f26v
• Referencehttps://cna.erlef.org/cves/CVE-2026-107685.html
• Referencehttps://osv.dev/vulnerability/EEF-CVE-2026-107685
• Referencehttps://github.com/agentjido/req_llm/commit/a389d718640ceb2d541a8f540ab954cbf5ef8313