CVE Catalog

CVE-2026-62987

MediumCVSS 5.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.20%

9th percentile - higher than 9% of all known CVEs

Summary

Fabio versions 1.6.6 through 1.7.2 fail to protect operator-configured forwarding headers (ClientIPHeader, TLSHeader, RequestID) from removal by an unauthenticated client. The CVE-2025-48865 fix only covers a hardcoded set of headers, allowing attackers to manipulate these critical headers before they reach the backend.

Risk Assessment

Loss of client IP, TLS termination, and request correlation signals can potentially bypass authorization and auditing mechanisms, enabling attackers to hide malicious activities.

Recommendation

Update Fabio to version 1.7.2 or later, which addresses this issue.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS