PoC Monitor
← All CVEs
CVE-2026-77776published 21 Aug 2026 11:22 UTCData: JSON · API

Headroom Labs Headroom

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

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.3critical · scored by CNA · CWE-639
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Headroom Labs Headroom
  • < 0.36.1

Fixed in 0.36.1

Mitigation

Upgrade Headroom to 0.36.1 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published21 Aug 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.