CVEvulnerability

CVE-2026-16732

6.1 MEDIUM Published 2026-08-18 Modified 2026-09-02 Official page ↗
Status
Analyzed
Published
2026-08-18
Last modified
2026-09-02
Assigner
ce714d77-add3-4f53-aff5-83d477b104bb
CVSS 3.1 (ce714d77-add3-4f53-aff5-83d477b104bb)
6.1 MEDIUM — CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
Weaknesses
CWE-348

Description

fastify is a fast and low overhead web framework for Node.js. Impact: the fix for CVE-2026-3635 added a guard on the forwarded-header reads used to derive the request host, protocol, hostname, ip, and ips values, checking the connecting address. That guard closes the IP, CIDR, and custom-function forms of trustProxy correctly, because those forms compile to predicates that inspect the connecting address. The hop-count form, where trustProxy is set to a number, compiles to a predicate that structurally ignores the address, so the guard is always satisfied for any hop count of one or more. Applications configured with a numeric trustProxy value, such as trustProxy set to 1 for a single reverse proxy, remain vulnerable: an attacker who can reach the Fastify origin directly, bypassing the front-facing proxy, can spoof the forwarded request fields exactly as in the unpatched version. The impact class matches the parent CVE-2026-3635, including host injection in generated URLs, HTTPS-enforcement bypass, secure-cookie and CSRF-origin bypass, and host-based routing and cache poisoning. Affected versions are fastify from 5.8.3 up to but not including 5.12.1. Patches: patched in fastify 5.12.1, where the numeric form of trustProxy is disabled at runtime and removed from the TypeScript type union. Workarounds: migrate to an IP, CIDR, or custom-function trustProxy value that validates the connecting address, and ensure the Fastify origin is only reachable through the trusted proxy chain.

Affected configurations

• fastify fastify (>= 5.8.3 < 5.12.1)

Related

Weakness · CWE (1)

  • CWE-348 Use of Less Trusted Source weakness

References