CVE-2026-3635
Fastify ≤ 5.8.3
Raw vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:NSummary
CVE-2026-3635 is a medium-severity Use of Less Trusted Source (CWE-348) vulnerability in Fastify Fastify. Its CVSS base score is 6.1 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-14431
Vulnerability Data
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 —…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vuln in public-facing Fastify server allows direct header spoofing of X-Forwarded-Proto/Host to bypass trustProxy checks, directly enabling T1190 exploitation and facilitating T1557 MITM-style manipulation of security decisions (protocol/host).
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation of X-Forwarded-Proto/Host headers against the trustProxy source-IP/subnet/function before they are used to derive request.protocol or request.host.
Enforces information-flow rules so that protocol/host values are only accepted from explicitly trusted proxy addresses, blocking spoofed headers from direct attacker connections.
Boundary-protection mechanisms can be configured to ensure all traffic reaching the application has already passed through the designated trusted proxy, eliminating the direct-connection attack path.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Explicit authenticity/integrity checks before use directly reduce selection of a less-trusted source.
Correlating multiple sources can surface discrepancies that discourage reliance on the less-trusted one.
Protecting data-in-transit integrity helps ensure the more-trusted source is the one whose data is accepted.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure architecture principles include trusted input channels and source verification mechanisms.
Security testing can detect and prevent acceptance of data from less-trusted sources during development.
Network security controls can enforce trusted data paths and source validation, reducing reliance on unverified inputs.
Secure network services include source validation and integrity checks that help prevent acceptance of data from less-trusted origins.
Application security requirements can mandate trusted data sources and input validation, directly addressing the weakness.
Secure coding practices can enforce checks that prefer or validate the more trusted data source.
Hardening callouts derived
Configuration rules from DISA STIG baselines that reduce the attack surface for weaknesses of the type cited by this CVE. Derived transitively via CVE→CWE→STIG over `controls_xwalks` (authoritative rows only).
Oracle Linux 8 (1 rule)
- V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. via CWE-348
Oracle Linux 9 (1 rule)
- V-271525 OL 9 must have GPG signature verification enabled for all software repositories. via CWE-348