Approved changes feed: RSS · Atom

cpe:2.3:a:fabiolb:fabio:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorFabiolb (f5d5ad9a-1a15-5492-b135-d9b307e27474)
ProductFabio (0affb2bc-327a-515a-b3b1-1536a9a989dd)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/fabiolb/fabio purl2cpe 2026-06-01 10:11:09.320099
pkg:golang/github.com/fabiolb/fabio purl2cpe 2026-06-01 10:11:09.320103

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-62987 vulnerable 2026-10-13 12:28:41.283402 Fabio - Incomplete fix for CVE-2025-48865: operator-configured trust headers (clientip/tls/requestid) still strippable via the Connection header
MEDIUM (5.8)
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.
Published: 2026-09-21T16:11:21.044Z
Updated: 2026-09-21T18:04:03.288Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-48865 vulnerable 2026-06-08 07:29:12.117955 Fabio allows HTTP clients to manipulate custom headers it adds
CRITICAL (9.1)
Fabio is an HTTP(S) and TCP router for deploying applications managed by consul. Prior to version 1.6.6, Fabio allows clients to remove X-Forwarded headers (except X-Forwarded-For) due to a vulnerability in how it processes hop-by-hop headers. Fabio adds HTTP headers like X-Forwarded-Host and X-Forwarded-Port when routing requests to backend applications. Since the receiving application should trust these headers, allowing HTTP clients to remove or modify them creates potential security vulnerabilities. Some of these custom headers can be removed and, in certain cases, manipulated. The attack relies on the behavior that headers can be defined as hop-by-hop via the HTTP Connection header. This issue has been patched in version 1.6.6.
Published: 2025-05-30T06:14:45.819Z
Updated: 2025-05-30T12:24:19.086Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.