p PatchFirst

CVE-2026-3635

CVE-2026-3635 · Fastify request.protocol and request.host spoofable via X-Forwarded-Proto/Host from untrusted connections when trustProxy uses restrictive trust function

This page contains facts from public vulnerability sources. Check the original advisory before updating.

Summary When trustProxy is configured with a restrictive trust function (e.g., a specific IP like trustProxy: '10.0.0.1', a subnet, a hop count, or a custom function), the request.protocol and request.host getters read X-Forwarded-Proto and X-Forwarded-Host headers from any connection — including connections from untrusted IPs. This allows an attacker connecting directly to Fastify (bypassing the proxy) to spoof both the protocol and host seen by the application. Affected Versions fastify <= 5.8.2 Impact Applications using request.protocol or request.host for security decisions (HTTPS enforcement, secure cookie flags, CSRF origin checks, URL construction, host-based routing) are affected when trustProxy is configured with a restrictive trust function. When trustProxy: true (trust everything), both host and protocol trust all forwarded headers — this is expected behavior. The vulnerability only manifests with restrictive trust configurations.

CVSS 6.1 · Medium · EPSS 0.2% · Fix available

Published
Updated

Stack: node

Affected products and versions

  • fastify

    Versions
    • ≥ 0, ≤ 5.8.2: Affected (semver)
    • 5.8.3: Not affected (semver)

    Update to 5.8.3

  • fastify npm

    Affected ranges
    • SEMVER: < 5.8.3

    Update to 5.8.3

Original sources

Check your server →