CVE-2026-107685
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
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.
Fixes and workarounds
Workaround
Leave the openai_stream_transport provider option at its default :sse for the OpenAI and OpenAI Codex providers, and do not call ReqLLM.Providers.OpenAI.WebSocket.start_responses_session/2 directly. Responses streaming then runs over HTTP through Finch, which verifies certificates. ReqLLM.OpenAI.Realtime.connect/2 has no HTTP alternative, so do not use it on an affected version.
Source: CNA: EEFFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: EEFAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| req_llm agentjido req_llm
hex |
≥ 1.9.0; < 1.29.0 (affected, semver)
Other versions: unaffected |
CNA: EEF |
| req_llm agentjido agentjido/req_llm
github |
≥ a389d718640ceb2d541a8f540ab954cbf5ef8313; < c7264fc0217fbacfb5562234ff790b8e4462de76 (affected, git)
Other versions: unaffected |
CNA: EEF |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 9.1 critical |
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N | CNA: EEF |
Exploit evidence
- https://github.com/agentjido/req_llm/security/advisories/GHSA-6vww-5m28-f26v
exploit · ADP: CISA-ADP
References
- https://github.com/agentjido/req_llm/security/advisories/GHSA-6vww-5m28-f26vCNA: EEF · vendor-advisory, related
- https://cna.erlef.org/cves/CVE-2026-107685.htmlCNA: EEF · related
- https://osv.dev/vulnerability/EEF-CVE-2026-107685CNA: EEF · related
- https://github.com/agentjido/req_llm/commit/a389d718640ceb2d541a8f540ab954cbf5ef8313CNA: EEF · related
- https://github.com/agentjido/req_llm/commit/c7264fc0217fbacfb5562234ff790b8e4462de76CNA: EEF · patch
- https://github.com/agentjido/req_llm/security/advisories/GHSA-6vww-5m28-f26vADP: CISA-ADP · exploit
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.