Vulnerabilities

Vulnerability · CVE-2026-107685

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

Published Oct 23, 2026 · catalog updated Oct 23, 2026 · WebSocket sessions do not

Last checked Nov 6, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-107685. EPSS is 0.27%. Act only if a listed version of WebSocket sessions do not is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (WebSocket sessions do not).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.27%
Remediation
Advisory link
Affected products
Hex req_llm · vendor agentjido req_llm

## Summary 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 bearer token, via a TLS certificate the client does not trust. in starts WebSockex without TLS options, and WebSockex defaults to , which connects with . The option allowlist also drops any caller-supplied or , 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 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. ## Details **1. Entry points.** and , and the Codex provider's , turn the provider base URL into a URL and start with an header that carries the OpenAI API key or the OAuth access token. **2. Missing TLS options.** passes only the headers and the timeouts to , and the allowlist in forwards only , , , , and the socket timeouts to . No , , or value reaches WebSockex, and a caller cannot inject one. **3. Insecure default.** WebSockex 0.5.1 sets when the option is absent and opens the connection through with . Any certificate completes the handshake, so an attacker who terminates TLS on the path receives the upgrade request with the bearer token and every frame of the session, and can rewrite frames in either direction. ## Proof of concept 1. Start a TLS endpoint on with a self-signed certificate chain that no trust store contains, and let it answer the WebSocket upgrade with . 2. On a vulnerable version, call with and , then . 3. returns , the endpoint completes the TLS handshake, and the endpoint receives the upgrade request carrying the bearer token. On 1.29.0 the same call returns and the endpoint never sees the request. ## Impact An attacker on the network path between an application and the OpenAI endpoint presents thei

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Hex req_llm1.9.0 → 1.29.0
  • vendor agentjido req_llmversion unspecified

How to fix CVE-2026-107685

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-107685. EPSS is 0.27%. Act only if a listed version of WebSocket sessions do not is installed.

Which versions are affected?

Compare what you have installed with 1.9.0 → 1.29.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-295: Improper Certificate Validation. EPSS 0.27%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 23, 2026 · GitHub Advisory Database

    Detected

    ## Summary 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 bearer token, via a TLS certificate the client does not trust. in starts WebSockex without TLS options, and WebSockex defaults to , which connects with . The option allowlist also drops any caller-supp

  2. Oct 23, 2026 · GitHub Advisory Database

    Fix available

    req_llm fixed in 1.29.0

  3. Oct 23, 2026 · GitHub Advisory Database

    Fix available

    req_llm fixed in 1.29.0

  4. Oct 23, 2026 · GitHub Advisory Database

    Updated

    ## Summary 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 bearer token, via a TLS certificate the client does not trust. in starts WebSockex without TLS options, and WebSockex defaults to , which connects with . The option allowlist also drops any caller-supp

Sources

  • CVE.orgVulnerability recordCVE-2026-107685

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

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-107685

    30-day exploitation probability 0.27%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-6vww-5m28-f26v

    GitHub Advisory Database record mirrored by OSV.

    github.com
  • OpenSSF OSV / OSV ScannerPackage advisoryEEF-CVE-2026-107685

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

    osv.dev

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 6, 2026
  • GitHub Advisory DatabaseOct 26, 2026
  • OpenSSF OSV / OSV ScannerOct 26, 2026
  • CVE.orgOct 23, 2026