req_llm
Composable Elixir library for LLM interactions built on Req and Finch
Activity
- Latest release
- 6d ago
- Total releases
- 43
- Cadence
- ~7 days
- Last 12 months
- 35
Reach
- Downloads
- 750.6k
- Stars
- 602
Details
- License
- Apache-2.0
- First release
- Sep 14, 2025
| Version | Released | |
|---|---|---|
1.29.0
minor
| ||
1.28.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.27.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.26.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.25.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.24.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.23.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.22.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.21.1
patch
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.21.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.20.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.19.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.18.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.17.1
patch
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.17.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.16.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.15.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.14.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.13.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.12.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.11.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.10.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.9.0
minor
1 CVE
CVE-2026-107685
EEF-CVE-2026-107685
GHSA-6vww-5m28-f26v
Oct 23, 2026
WebSocket sessions do not verify TLS certificates, exposing API keys and OAuth tokens to on-path attackers
Critical
Network
Low
None
None
SummaryImproper 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 The OpenAI Responses, Realtime, and Codex WebSocket paths reach this client and send the API key or OAuth access token in the This issue affects req_llm: from 1.9.0 before 1.29.0. Details1. Entry points. 2. Missing TLS options. 3. Insecure default. WebSockex 0.5.1 sets Proof of concept
ImpactAn attacker on the network path between an application and the OpenAI endpoint presents their own certificate, obtains the OpenAI API key or OAuth access token and the full session content, and can alter model output and tool calls before the application acts on them. Every application that uses the OpenAI Responses, Realtime, or Codex WebSocket paths is affected. WorkaroundsLeave the Affected versions
1.10.0
1.11.0
1.12.0
1.13.0
1.14.0
1.15.0
1.16.0
1.17.0
1.17.1
1.18.0
1.19.0
1.20.0
+ 10 more Show less
1.21.0
1.21.1
1.22.0
1.23.0
1.24.0
1.25.0
1.26.0
1.27.0
1.28.0
1.9.0
Fixed in
1.29.0
References
Updated Oct 23, 2026 · Source: OSV.dev | ||
1.8.0
minor
| ||
1.7.1
patch
| ||
1.7.0
minor
| ||
1.6.0
minor
| ||
1.5.1
patch
| ||
1.5.0
minor
| ||
1.4.1
patch
| ||
1.4.0
minor
| ||
1.3.0
minor
| ||
1.2.0
minor
| ||
1.1.0
minor
| ||
1.0.0
initial
| ||
1.0.0-rc.8
pre
| ||
1.0.0-rc.7
pre
|
1.0.0-rc.7
pre
Dependencies (9)
+ 1 more
Changelog
Compare changes
|
|
1.0.0-rc.6
pre
| ||
1.0.0-rc.5
pre
| ||
1.0.0-rc.4
pre
| ||
1.0.0-rc.3
pre
| ||
1.0.0-rc.2
pre
| ||
1.0.0-rc.1
pre
|