[ CVE-2026-62987 · Published 21 Sep 2026 ]
Fabio - Incomplete fix for CVE-2025-48865: operator-configured trust headers (clientip/tls/requestid) still strippable via the Connection header
[ Why it matters ]Priority signals
- Public proof-of-concept exploit exists (CISA SSVC)
[ Description ]Official 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.
[ Fixes ]Fixes and patches
- github.com/fabiolb/fabio 1.7.2Fixed version · GitHub Advisories · go package github.com/fabiolb/fabio: upgrade to 1.7.2 or later (affected >= 1.6.6, <= 1.7.1)
[ Packages ]Affected open-source packages
- github.com/fabiolb/fabio goAffected >= 1.6.6, <= 1.7.1 · fixed in 1.7.2 · GHSA-fq95-v8xc-jm3v
[ References ]References
- github.com/fabiolb/fabio/security/advisories/GHSA-fq95-v8xc-jm3vx_refsource_CONFIRM
- github.com/fabiolb/fabio/commit/240526a8004077edad4fb96d25b382bfc3901357x_refsource_MISC
- github.com/fabiolb/fabio/releases/tag/v1.7.2x_refsource_MISC