{"answers":{"affected":"3 open source packages ship an affected version, including github.com/fabiolb/fabio.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62987 exists.","fix":"Upgrade github.com/fabiolb/fabio to 1.7.2 or later.","what":"CVE-2026-62987 is a medium-severity vulnerability in fabiolb fabio, published on 21 Sep 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-62987 and fix it if it is affected.\n\nWhat it is: CVE-2026-62987 is a medium-severity vulnerability in fabiolb fabio, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62987 exists.\n\nAffected packages and fixed versions:\n- github.com/fabiolb/fabio (Go): affected from 1.6.6; fixed in 1.7.2\n- github.com/fabiolb/fabio (Go): affected from 1.6.6; fixed in 1.7.2\n- github.com/fabiolb/fabio (Go): affected from 1.6.6; fixed in 1.7.2\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-62987/ (Markdown: https://insights.sbomify.com/CVE-2026-62987/index.md)","id":"CVE-2026-62987","markdown":"https://insights.sbomify.com/CVE-2026-62987/index.md","name":"CVE-2026-62987","record":{"aliases":["GHSA-fq95-v8xc-jm3v","GO-2026-6566","UBUNTU-CVE-2026-62987"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"HTTP/TCP router","requires_auth":"none","summary":"Attackers can strip operator-configured trust headers via the Connection header, bypassing backend authorization and auditing mechanisms in Fabio deployments.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-348","name":"Use of Less Trusted Source"},{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"Fabio is an HTTP(S) and TCP router for deploying applications managed by consul. From 1.6.6 until 1.7.2, the CVE-2025-48865 fix in proxy/http_headers.go uses protectHeaders for a hardcoded set of forwarded headers but omits the operator-configured ClientIPHeader, TLSHeader, and RequestID names. In proxy/http_proxy.go, HTTPProxy.ServeHTTP calls addHeaders to set these trust headers before Go ReverseProxy processes the inbound Connection header, allowing an unauthenticated client to name and remove the configured headers before the request reaches the backend. Deployments that enable the corresponding proxy.header options can therefore lose client-IP, TLS-termination, or request-correlation signals used by backend authorization and auditing; the options are empty by default, and the hardcoded protected forwarded headers are unaffected. This issue is fixed in version 1.7.2.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Fabio - Incomplete fix for CVE-2025-48865: operator-configured trust headers (clientip/tls/requestid) still strippable via the Connection header","id":"CVE-2026-62987","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Froxlor: Credential and 2FA secret disclosure via Froxlor API endpoints","id":"CVE-2026-62988"},"packages":[{"ecosystem":"Go","fixed":["1.7.2"],"introduced":["1.6.6"],"last_affected":[],"package":"github.com/fabiolb/fabio","purl":null,"source":"GHSA-fq95-v8xc-jm3v"},{"ecosystem":"Go","fixed":["1.7.2"],"introduced":["1.6.6"],"last_affected":[],"package":"github.com/fabiolb/fabio","purl":"pkg:golang/github.com/fabiolb/fabio","source":"GHSA-fq95-v8xc-jm3v"},{"ecosystem":"Go","fixed":["1.7.2"],"introduced":["1.6.6"],"last_affected":[],"package":"github.com/fabiolb/fabio","purl":"pkg:golang/github.com/fabiolb/fabio","source":"GO-2026-6566"}],"prev":{"headline":"OpenEXR: PyOpenEXR deep prefixed RGB stale lane disclosure","id":"CVE-2026-62986"},"products":["fabio"],"published":"2026-09-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["fabiolb"]},"summary":"Attackers can strip operator-configured trust headers via the Connection header, bypassing backend authorization and auditing mechanisms in Fabio deployments.","url":"https://insights.sbomify.com/CVE-2026-62987/"}