Lucene search
+L

8 matches found

Vulnrichment
Vulnrichment
•added 2026/08/21 11:22 a.m.•17 views

CVE-2026-77776 Headroom Proxy Treats the Client-Supplied x-headroom-user-id Header as an Authenticated Identity

Headroom's LLM proxy derives the memory owner from the x-headroom-user-id request header. The header is read directly at several points in headroom/proxy/handlers/openai.py, including the chat completion and websocket paths, and nothing binds the value to the caller. A client can therefore name...

9.3CVSS5.4AI score0.00613EPSS
SaveExploits0References5
Cvelist
Cvelist
•added 2026/08/21 11:22 a.m.•39 views

CVE-2026-77775 Headroom Proxy Sends Upstream Requests to a Client-Supplied Base URL Without Address Validation

Headroom's LLM proxy lets a client choose the upstream destination with the x-headroom-base-url request header. resolveopenaiupstreambase in headroom/proxy/handlers/openai.py accepts the header value, requires only that it parse with an http or https scheme and a hostname, and returns it for use ...

8.6CVSS0.00593EPSS
SaveExploits0References5
CVE
CVE
•added 2026/08/21 11:22 a.m.•67 views

CVE-2026-77776

Headroom LLM proxy (v0.29.0 and earlier) trusts the client-supplied x-headroom-user-id header as an authenticated identity without binding it to the caller. The header is read directly in headroom/proxy/handlers/openai.py across chat completion and websocket paths, allowing any client to imperson...

9.3CVSS5.5AI score0.00613EPSS
SaveExploits0References5
Cvelist
Cvelist
•added 2026/08/21 11:22 a.m.•41 views

CVE-2026-77776 Headroom Proxy Treats the Client-Supplied x-headroom-user-id Header as an Authenticated Identity

Headroom's LLM proxy derives the memory owner from the x-headroom-user-id request header. The header is read directly at several points in headroom/proxy/handlers/openai.py, including the chat completion and websocket paths, and nothing binds the value to the caller. A client can therefore name...

9.3CVSS0.00613EPSS
SaveExploits0References5
CVE
CVE
•added 2026/08/21 11:22 a.m.•47 views

CVE-2026-77775

Headroom LLM proxy (headroomlabs-ai/headroom) is vulnerable to SSRF via the x-headroom-base-url request header. The functions _resolve_openai_upstream_base and _select_passthrough_base_url accept any URL with an http/https scheme and hostname without rejecting loopback, link-local, or RFC 1918 de...

8.6CVSS5.8AI score0.00593EPSS
SaveExploits0References5
OSV
OSV
•added 2026/08/21 11:22 a.m.•21 views

CVE-2026-77776 Headroom Proxy Treats the Client-Supplied x-headroom-user-id Header as an Authenticated Identity

Headroom's LLM proxy derives the memory owner from the x-headroom-user-id request header. The header is read directly at several points in headroom/proxy/handlers/openai.py, including the chat completion and websocket paths, and nothing binds the value to the caller. A client can therefore name...

9.3CVSS5.6AI score
SaveExploits0References8
Vulnrichment
Vulnrichment
•added 2026/08/21 11:22 a.m.•15 views

CVE-2026-77775 Headroom Proxy Sends Upstream Requests to a Client-Supplied Base URL Without Address Validation

Headroom's LLM proxy lets a client choose the upstream destination with the x-headroom-base-url request header. resolveopenaiupstreambase in headroom/proxy/handlers/openai.py accepts the header value, requires only that it parse with an http or https scheme and a hostname, and returns it for use ...

8.6CVSS5.4AI score0.00593EPSS
SaveExploits0References5
OSV
OSV
•added 2026/08/21 11:22 a.m.•35 views

CVE-2026-77775 Headroom Proxy Sends Upstream Requests to a Client-Supplied Base URL Without Address Validation

Headroom's LLM proxy lets a client choose the upstream destination with the x-headroom-base-url request header. resolveopenaiupstreambase in headroom/proxy/handlers/openai.py accepts the header value, requires only that it parse with an http or https scheme and a hostname, and returns it for use ...

7.7CVSS5.5AI score
SaveExploits0References8
Rows per page
Query Builder