https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 12:19:07 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-366848 EUVD-2026-366848 https://cve.radiocsirt.org/vuln/euvd-2026-366848 https://cve.radiocsirt.org/vuln/fkie_cve-2026-71416 <p>Headroom compresses data before the data reaches a large language model. Prior to version 0.35.0, the Headroom WebSocket server does not validate the `Origin` header of incoming client WebSocket requests before forwarding the request to the upstream server, allowing malicious WebSocket clients to perform arbitrary LLM requests without authentication. This can be exploited by a malicious WebSocket client executed in a traditional or headless browser such as lightpanda, if the browser has access to the Headroom proxy and the OpenAI API key is stored in the `OPENAI_API_KEY` environment variable. Version 0.35.0 fixes the issue.</p> <p>Headroom compresses data before the data reaches a large language model. Prior to version 0.35.0, the Headroom WebSocket server does not validate the `Origin` header of incoming client WebSocket requests before forwarding the request to the upstream server, allowing malicious WebSocket clients to perform arbitrary LLM requests without authentication. This can be exploited by a malicious WebSocket client executed in a traditional or headless browser such as lightpanda, if the browser has access to the Headroom proxy and the OpenAI API key is stored in the `OPENAI_API_KEY` environment variable. Version 0.35.0 fixes the issue.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-71416 https://cve.radiocsirt.org/vuln/ghsa-h46j-26q3-rggf <p><strong>Affected:</strong> PyPI: headroom-ai</p> <p>### Summary The Headroom WebSocket server does not validate the `Origin` header of incoming client WebSocket requests before forwarding the request to the upstream server, allowing malicious WebSocket clients to perform arbitrary LLM requests without authentication. This can be exploited by a malicious WebSocket client executed in a traditional or headless browser such as lightpanda, if the browser has access to the Headroom proxy and the OpenAI API key is stored in the `OPENAI_API_KEY` environment variable.</p> <p>### Details The Headroom server defines a WebSocket handler at `ws://&lt;headroom_host&gt;:8787/v1/responses` in `headroom/providers/proxy_routes.py`: ```python @app.websocket(&#34;/v1/responses&#34;) async def openai_responses_ws(websocket: WebSocket): await proxy.handle_openai_responses_ws(websocket) ``` In the `handle_openai_responses_ws()` method of the `OpenAIHandlerMixin` class, the `Origin` header of the WebSocket client handshake is not checked or verified before calling `websocket.accept()`, which grants any WebSocket client (including malicious clients) access to the server: ```python async def handle_openai_responses_ws(self, websocket: WebSocket) -&gt; None: &#34;&#34;&#34;WebSocket proxy for /v1/responses (Codex gpt-5.4+).</p> <p>Newer Codex versions use WebSocket instead of HTTP POST for the Responses API. This handler: 1. Accepts the client WebSocket 2. Receives the first message (``response.create`` request) 3. Opens an…</p> <p><strong>Affected:</strong> PyPI: headroom-ai</p> <p>### Summary The Headroom WebSocket server does not validate the `Origin` header of incoming client WebSocket requests before forwarding the request to the upstream server, allowing malicious WebSocket clients to perform arbitrary LLM requests without authentication. This can be exploited by a malicious WebSocket client executed in a traditional or headless browser such as lightpanda, if the browser has access to the Headroom proxy and the OpenAI API key is stored in the `OPENAI_API_KEY` environment variable.</p> <p>### Details The Headroom server defines a WebSocket handler at `ws://&lt;headroom_host&gt;:8787/v1/responses` in `headroom/providers/proxy_routes.py`: ```python @app.websocket(&#34;/v1/responses&#34;) async def openai_responses_ws(websocket: WebSocket): await proxy.handle_openai_responses_ws(websocket) ``` In the `handle_openai_responses_ws()` method of the `OpenAIHandlerMixin` class, the `Origin` header of the WebSocket client handshake is not checked or verified before calling `websocket.accept()`, which grants any WebSocket client (including malicious clients) access to the server: ```python async def handle_openai_responses_ws(self, websocket: WebSocket) -&gt; None: &#34;&#34;&#34;WebSocket proxy for /v1/responses (Codex gpt-5.4+).</p> <p>Newer Codex versions use WebSocket instead of HTTP POST for the Responses API. This handler: 1. Accepts the client WebSocket 2. Receives the first message (``response.create`` request) 3. Opens an…</p> https://cve.radiocsirt.org/vuln/ghsa-h46j-26q3-rggf