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

Critical 9.1 Published Updated
Exploited in the wild
Not known
Fix
Available

What is CVE-2026-107685?

CVE-2026-107685 is a critical vulnerability in agentjido req_llm, published on 23 Oct 2026.

Official 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.

Weakness: CWE-295

Which versions are affected by CVE-2026-107685?

1 open source package ship an affected version, including req_llm.

PackageAffectedFixed in
req_llm HexFrom 1.9.01.29.0

How do I fix CVE-2026-107685?

Upgrade req_llm to 1.29.0 or later.

Is CVE-2026-107685 being exploited?

There is no known exploitation of CVE-2026-107685 in the wild and no public exploit code.

Sources

Also known as EEF-CVE-2026-107685, GHSA-6vww-5m28-f26v, GHSA-w53j-6pxf-r2vw.

Is CVE-2026-107685 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free