{
  "id": 18670337,
  "title": "Forwarded Without Question: How Web Frameworks Overtrust the Forwarded Header",
  "url": "https://urgent.news/2026/11/07/forwarded-without-question-how-web-frameworks-overtrust-the-forwarded",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-07T06:18:48.000Z",
  "source": {
    "name": "Lobsters",
    "slug": "lobsters",
    "url": "https://www.lkoskela.fi/blog/2026-11-05-forwarded-without-question/"
  },
  "original_language": "en",
  "account": "The article examines the risks associated with the Forwarded header in web applications, particularly when web frameworks and reverse proxies overtrust this header. The Forwarded header, defined in RFC 7239, is intended to replace the non-standard X-Forwarded-* headers and provides standardized information about the client IP address, original host name, and request protocol.\n\nHowever, the article highlights that many web frameworks, including Rails, Spring, and Jetty, read values from the Forwarded header in their default configurations. This can lead to client IP and request host name spoofing if these headers are trusted without proper validation. The issue arises because most reverse proxies, CDNs, and middleware servers do not modify the Forwarded header in requests, allowing untrusted values to be passed directly to web applications.\n\nThe article suggests that developers and administrators should ensure that proxies and applications agree on the headers that are trusted and configure proxies to drop any untrusted proxy headers. The Forwarded header combines multiple X-F headers into one, but its adoption is still limited, as it requires support from both web frameworks and middleware servers. The article notes that the lack of real benefits over X-F headers and the relatively recent adoption of Forwarded have limited its widespread use.\n\nThe risks of Forwarded header misuse are well-documented, with examples of how attackers could exploit overlapping information from X-F and Forwarded headers to bypass IP address restrictions, rate limits, and password reset email defenses. The article concludes by stating that trusted proxy configurations are crucial in preventing such spoofing attacks, but these mechanisms are ineffective if the proxy itself passes sensitive headers to the backend application without proper validation.",
  "summary": null,
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}