• Sources: primary, discussion
  • Summary: Lauri Koskela found that Jetty 12.1.7, Spring Boot 4.0.5 with Jetty, Reactor Netty or the FRAMEWORK strategy, and Rails 8.1.3 parse RFC 7239 Forwarded and prioritise it over X-Forwarded-* headers, while Envoy, ingress-nginx, Traefik, Apache, Caddy and Kong pass Forwarded through untouched. This lets clients spoof client IP, host name and scheme behind a trusted proxy. Rails fixed its spoofing check in 8.1.4.1, Spring Boot 4.2 now parses only X-Forwarded-* by default, and Jetty kept its default while adding configuration options.
  • Why it matters: Spring and Jetty services behind a proxy that does not strip Forwarded can have IP allowlists, rate limits and password reset host names bypassed, so proxies should drop untrusted forwarding headers.