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.
Published: 2026-10-23
Score: 9.1 Critical
EPSS: n/a
KEV: No
Impact: Credential exposure from TLS verification bypass on WebSocket sessions
Action: Apply Workaround
AI Analysis

Impact

The CVE describes an improper certificate validation flaw in the WebSocket streaming client of the agentjido req_llm library. Because the client ignores TLS certificate verification, an attacker on the network path can present a forged certificate and intercept the WebSocket connection. The bearer token or OAuth access token is transmitted in the Authorization header, so the attacker can read and modify it, effectively compromising authentication credentials and enabling unauthorized access to OpenAI services. This weakness is a classic Improper Certificate Validation (CWE‑295) and undermines both confidentiality and integrity of the credentials.

Affected Systems

Applications that depend on agentjido req_llm versions 1.9.0 through 1.28.x are vulnerable. The library’s WebSocket paths are used for OpenAI Responses, Realtime, and Codex streaming, so any deployment that invokes these endpoints within the affected version range is impacted. Systems that embed the library for streaming or realtime OpenAI interactions are thus at risk.

Risk and Exploitability

The CVSS score of 9.1 categorizes the vulnerability as critical. Although an EPSS score is not available, the exploitability remains high because the flaw requires only a TLS man‑in‑the‑middle capability, a common scenario for on‑path adversaries. The vulnerability is not currently listed in the CISA KEV catalog, but the lack of certificate verification directly exposes bearer tokens. Based on the description, the attack vector is inferred to be a network‑based MITM that intercepts the insecure WebSocket traffic.

Generated by OpenCVE AI on October 23, 2026 at 12:50 UTC.

Remediation

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


OpenCVE Recommended Actions

  • Set the openai_stream_transport provider option to its default value (sse) so that streaming occurs over HTTP, which enforces certificate verification.
  • Avoid calling ReqLLM.Providers.OpenAI.WebSocket.start_responses_session/2 directly in application code to prevent bypassing TLS checks.
  • Do not use ReqLLM.OpenAI.Realtime.connect/2 with affected req_llm versions, as this function has no HTTP alternative and will expose tokens.
  • If possible, upgrade the library to version 1.29.0 or later, which removes the vulnerability by default.

Generated by OpenCVE AI on October 23, 2026 at 12:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 23 Oct 2026 11:15:00 +0000

Type Values Removed Values Added
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.
Title WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
First Time appeared Agentjido
Agentjido req Llm
Weaknesses CWE-295
CPEs cpe:2.3:a:agentjido:req_llm:*:*:*:*:*:*:*:*
Vendors & Products Agentjido
Agentjido req Llm
References
Metrics cvssV4_0

{'score': 9.1, 'vector': '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'}


Subscriptions

Agentjido Req Llm
cve-icon MITRE

Status: PUBLISHED

Assigner: EEF

Published:

Updated: 2026-10-23T11:00:38.975Z

Reserved: 2026-10-10T13:15:02.316Z

Link: CVE-2026-107685

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-23T12:18:06.410

Modified: 2026-10-23T12:18:06.410

Link: CVE-2026-107685

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-23T13:00:18Z

Weaknesses
  • CWE-295

    Improper Certificate Validation