{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-77775 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-77775 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77775 is a high-severity server-side request forgery 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-77775 and fix it if it is affected.\n\nWhat it is: CVE-2026-77775 is a high-severity server-side request forgery 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-77775 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-77775/ (Markdown: https://insights.sbomify.com/CVE-2026-77775/index.md)","id":"CVE-2026-77775","markdown":"https://insights.sbomify.com/CVE-2026-77775/index.md","name":"CVE-2026-77775","record":{"aliases":["GHSA-4j5r-9p93-j2px"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"LLM proxy server","requires_auth":"none","summary":"Attackers can force the proxy to send requests to internal or cloud metadata services via a client-supplied header, disclosing sensitive data.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Headroom's LLM proxy lets a client choose the upstream destination with the x-headroom-base-url request header. _resolve_openai_upstream_base 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 as the upstream base; _select_passthrough_base_url in headroom/providers/proxy_routes.py reads the same header for the passthrough routes. No check rejects loopback, link-local, or RFC 1918 destinations, and because the component is a proxy the upstream response is returned to the caller, so the request reaches internal services and cloud metadata addresses and their responses are disclosed. The Authorization header accompanying the request is forwarded unchanged to the caller-designated host. 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 Sends Upstream Requests to a Client-Supplied Base URL Without Address Validation","id":"CVE-2026-77775","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Headroom Proxy Treats the Client-Supplied x-headroom-user-id Header as an Authenticated Identity","id":"CVE-2026-77776"},"packages":[],"prev":{"headline":"Adobe Commerce | Incorrect Authorization (CWE-863)","id":"CVE-2026-77774"},"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":"partial"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["Headroom Labs"]},"summary":"Attackers can force the proxy to send requests to internal or cloud metadata services via a client-supplied header, disclosing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-77775/"}