{"id":"CVE-2026-77776","aliases":[],"url":"https://o3.security/vulnerability/CVE-2026-77776","summary":"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…","details":"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 another user's identifier and read or write that user's stored LLM memory. The fix introduces a single resolve_memory_identity seam in headroom/proxy/identity.py that honors the header only for loopback or allowlisted callers and otherwise binds the identity to the proxy-token fingerprint or the operating system user. The pip console script binds 127.0.0.1 by default, but the reference docker-compose.yml ships --host 0.0.0.0 with published ports and no required HEADROOM_PROXY_TOKEN, which the server itself warns about at startup, so a deployment following the shipped compose exposes the affected data-plane routes to the network without authentication.","published":"2026-08-21T12:16:36.967","modified":"2026-08-21T12:16:36.967","cvss":{"score":9.1,"severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"},"epss":null,"cisaKev":null,"exploitsKnown":null,"affectedPackages":[],"fix":{"url":"https://github.com/headroomlabs-ai/headroom/pull/2207","label":"headroomlabs-ai/headroom#2207"},"references":[{"type":"WEB","url":"https://github.com/headroomlabs-ai/headroom"},{"type":"WEB","url":"https://github.com/headroomlabs-ai/headroom/blob/v0.29.0/headroom/proxy/handlers/openai.py"},{"type":"WEB","url":"https://github.com/headroomlabs-ai/headroom/blob/v0.36.1/headroom/proxy/identity.py"},{"type":"WEB","url":"https://github.com/headroomlabs-ai/headroom/pull/2207"},{"type":"WEB","url":"https://www.vulncheck.com/advisories/headroom-proxy-treats-the-client-supplied-x-headroom-user-id-header-as-an-authenticated-identity"}],"provenance":{"sources":["OSV.dev","NVD","FIRST.org (EPSS)"],"lastVerified":"2026-08-21T12:16:36.967"}}