chi Allows Host Header Injection which Leads to Open Redirect in RedirectSlashes
CVE-2025-71405GHSA-vrw8-fxc6-2r93
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/go-chi/chi/v5 5.2.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- <= 5.2.1
- Fixed in
- 5.2.2
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-vrw8-fxc6-2r93 lists affected ranges: Go github.com/go-chi/chi/v5 >=0 <=5.2.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2025-71405: 0.39% estimated exploitation activity in the next 30 days; percentile 33.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary The RedirectSlashes function in middleware/strip.go is vulnerable to host header injection which leads to open redirect. We consider this a lower-severity open redirect, as it can't be exploited from browsers or email clients (requires manipulation of a Host header). Details The RedirectSlashes method uses the Host header to construct the redirectURL at this line https://github.com/go-chi/chi/blob/master/middleware/strip.go#L55 The Host header can be manipulated by a user to be any arbitrary host. This leads to open redirect when using the RedirectSlashes middleware PoC Create a simple server which uses the RedirectSlashes middleware Run the server go run main.go Once the server is running, send a request that will trigger the RedirectSlashes function with an arbitrary Host header curl -iL -H "Host: example.com" http://localhost:8080/test/ Observe that the request will be redirected to example.com Without the host header, the response is returned from the test server Impact…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-vrw8-fxc6-2r93
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-71405 Advisory: chi Allows Host Header Injection which Leads to Open Redirect in RedirectSlashes IDs: CVE-2025-71405, GHSA-vrw8-fxc6-2r93 Record: https://patchnext.com/advisories/cve-2025-71405 (revision 1, source checked 26 Oct 2026, 15:29 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/go-chi/chi/v5 5.2.2. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/go-chi/chi/v5: affected <= 5.2.1; fixed in 5.2.2 ## Suggested inspection (read-only) - Go github.com/go-chi/chi/v5: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/go-chi/chi/v5. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-vrw8-fxc6-2r93 (GitHub-reviewed advisory GHSA-vrw8-fxc6-2r93 lists affected ranges: Go github.com/go-chi/chi/v5 >=0 <=5.2.1) Commands are suggestions: review each one before running it.
Loading voting…