@fastify/reply-from vulnerable to connection header abuse enabling stripping of proxy-added headers
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9epss 0.4%
exploitation probability
0.4%top 62% of all CVEs
observed exploitation
nono source reports it
@fastify/reply-from v12.6.1 and earlier and @fastify/http-proxy v11.4.3 and earlier process the client's Connection header after the proxy has added its own headers via rewriteRequestHeaders. This allows attackers to retroactively strip proxy-added headers from upstream requests by listing them in the Connection header value. Any header added by the proxy for routing, access control, or security purposes can be selectively removed by a client. @fastify/http-proxy is also affected as it delegates to @fastify/reply-from.
Upgrade to @fastify/reply-from v12.6.2 or @fastify/http-proxy v11.4.4 or later.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:L/SI:H/SA:N
References
https://access.redhat.com/errata/RHSA-2026:10175https://access.redhat.com/security/cve/CVE-2026-33805https://bugzilla.redhat.com/show_bug.cgi?id=2458651https://cna.openjsf.org/security-advisories.htmlhttps://github.com/fastify/fastify-reply-from/security/advisories/GHSA-gwhp-pf74-vj37https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33805.json