What’s Vulnerable › Vulnerabilities

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

• Severity: critical (CVSS 9.1 v4.0)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.3% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-10-23 · updated 2026-10-23
• Weakness: CWE-295

Description

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.

Affected products

• agentjido req_llm: from 1.9.0 before 1.29.0 — fixed in 1.29.0

How to fix

Upgrade to a fixed version: agentjido req_llm 1.29.0. Check the vendor advisory for mitigations.

References

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

Get alerted when CVE-2026-107685 or the next vulnerability affects your stack