# CVE-2026-16732: fastify vulnerable to X-Forwarded-* spoofing under trustProxy hop-count > Attackers can spoof forwarded headers to bypass security controls like HTTPS enforcement and CSRF protection when using numeric trustProxy settings. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 18 Aug 2026 - **Updated:** 19 Aug 2026 - **Also known as:** GHSA-3m5p-2c4r-xxw2, MINI-72wj-4m78-5w2p ## What is CVE-2026-16732? CVE-2026-16732 is a medium-severity vulnerability in fastify, published on 18 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official 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. Weakness: CWE-348 (Use of Less Trusted Source) ## Which versions are affected by CVE-2026-16732? 2 open source packages ship an affected version, including fastify. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `fastify` | npm | From 5.8.3 | 5.12.1 | | `fastify` | npm | From 5.8.3 | 5.12.1 | Products: Fastify Fastify. ## How do I fix CVE-2026-16732? Upgrade fastify to 5.12.1 or later. ## Is CVE-2026-16732 being exploited? There is no known exploitation of CVE-2026-16732 in the wild and no public exploit code. ## Other vulnerabilities in fastify - [CVE-2026-84504](https://insights.sbomify.com/CVE-2026-84504/): fastify vulnerable to request body replacement via an async validation result collision (high 8.1) - [CVE-2026-76169](https://insights.sbomify.com/CVE-2026-76169/): fastify vulnerable to authentication bypass via malformed URLs reaching encapsulated not-found handlers (high 7.5) - [CVE-2026-84428](https://insights.sbomify.com/CVE-2026-84428/): fastify vulnerable to header validation bypass via incomplete schema case normalization (high 7.5) - [CVE-2026-84469](https://insights.sbomify.com/CVE-2026-84469/): fastify vulnerable to request validation bypass via skipped boolean false schemas (high 7.5) - [CVE-2026-33806](https://insights.sbomify.com/CVE-2026-33806/): fastify vulnerable to Body Schema Validation Bypass via Leading Space in Content-Type Header (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-16732 and fix it if it is affected. What it is: CVE-2026-16732 is a medium-severity vulnerability in fastify, published on 18 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-16732 in the wild and no public exploit code. Affected packages and fixed versions: - fastify (npm): affected from 5.8.3; fixed in 5.12.1 - fastify (npm): affected from 5.8.3; fixed in 5.12.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-16732/ (Markdown: https://insights.sbomify.com/CVE-2026-16732/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16732 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16732 - OSV: https://osv.dev/vulnerability/CVE-2026-16732 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-16732/ Summaries are generated and may contain mistakes; the official description above is the record.