{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-77776 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-77776 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77776 is a critical authentication bypass vulnerability in Headroom, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-77776 and fix it if it is affected.\n\nWhat it is: CVE-2026-77776 is a critical authentication bypass vulnerability in Headroom, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-77776 in the wild and no public exploit code.\n\nAffected product: Headroom. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-77776/ (Markdown: https://insights.sbomify.com/CVE-2026-77776/index.md)","id":"CVE-2026-77776","markdown":"https://insights.sbomify.com/CVE-2026-77776/index.md","name":"CVE-2026-77776","record":{"aliases":["GHSA-5vg3-c628-vf56"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"LLM proxy server","requires_auth":"none","summary":"Attackers can impersonate other users by spoofing the x-headroom-user-id header to read or modify their LLM memory, particularly in exposed Docker deployments.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Headroom Proxy Treats the Client-Supplied x-headroom-user-id Header as an Authenticated Identity","id":"CVE-2026-77776","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Missing authorization in Prospero Flow CRM","id":"CVE-2026-77780"},"packages":[],"prev":{"headline":"Headroom Proxy Sends Upstream Requests to a Client-Supplied Base URL Without Address Validation","id":"CVE-2026-77775"},"products":["Headroom"],"published":"2026-08-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["Headroom Labs"]},"summary":"Attackers can impersonate other users by spoofing the x-headroom-user-id header to read or modify their LLM memory, particularly in exposed Docker deployments.","url":"https://insights.sbomify.com/CVE-2026-77776/"}