CVE-2026-107685

ReqLLM WebSocket connections did not verify server certificates

agentjido · req_llm

First documented disclosure · Review checkpoint

Summary

An on-path attacker could read credentials and alter model sessions.

Severity and exploitation evidence

Critical · 9.1/10 · CVSS 4.0. Severity source.

Exploitation not established: Malicious exploitation remains unverified in the reviewed originals. A demonstration or absence from KEV does not establish exploitation status.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The WebSockex client defaulted to insecure TLS and the option allowlist discarded caller-supplied verification settings.

Conditions required

An on-path network position and an affected OpenAI Responses, Realtime or Codex WebSocket session.

Potential impact

API keys or OAuth tokens, prompts and tool output can be exposed; model output and tool calls can be changed. HTTP streaming and HTTP/2 duplex paths are unaffected.

Affected versions and configurations

req_llm: 1.9.0 through versions before 1.29.0.

Fix and mitigation status

1.29.0.

Practical next steps

Apply the issue-specific correction: 1.29.0. Restrict the affected tool or endpoint until the correction is deployed.

Operating lesson

Verify certificate chains and hostnames on every model transport.

Evidence and limits

Earliest reviewed public evidence 2026-10-22; CVE publication 2026-10-23. CVSS 4.0 9.1 is attributed to EEF in the CNA record.

Sources